WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:15.150 align:start position:0% [Music] 00:00:15.150 --> 00:00:15.160 align:start position:0% [Music] 00:00:15.160 --> 00:00:20.050 align:start position:0% [Music] okay<00:00:16.210> good<00:00:17.210> morning<00:00:17.570> everybody<00:00:18.940> today<00:00:19.940> I'm 00:00:20.050 --> 00:00:20.060 align:start position:0% okay good morning everybody today I'm 00:00:20.060 --> 00:00:22.090 align:start position:0% okay good morning everybody today I'm here<00:00:20.300> to<00:00:20.450> introduce<00:00:20.660> you<00:00:20.870> a<00:00:21.230> project<00:00:21.890> that<00:00:22.040> I 00:00:22.090 --> 00:00:22.100 align:start position:0% here to introduce you a project that I 00:00:22.100 --> 00:00:23.680 align:start position:0% here to introduce you a project that I really<00:00:22.430> wanted<00:00:22.700> to<00:00:22.820> see<00:00:23.030> implemented<00:00:23.360> on<00:00:23.660> the 00:00:23.680 --> 00:00:23.690 align:start position:0% really wanted to see implemented on the 00:00:23.690 --> 00:00:27.240 align:start position:0% really wanted to see implemented on the main<00:00:23.900> net<00:00:24.460> is<00:00:25.460> this<00:00:26.000> project<00:00:26.360> is<00:00:26.450> about 00:00:27.240 --> 00:00:27.250 align:start position:0% main net is this project is about 00:00:27.250 --> 00:00:31.300 align:start position:0% main net is this project is about implementing<00:00:28.250> real<00:00:29.090> world<00:00:29.390> supply<00:00:29.810> chain<00:00:30.310> for 00:00:31.300 --> 00:00:31.310 align:start position:0% implementing real world supply chain for 00:00:31.310 --> 00:00:34.420 align:start position:0% implementing real world supply chain for Italian<00:00:31.640> products<00:00:32.029> and<00:00:32.210> in<00:00:32.989> particular<00:00:33.500> we 00:00:34.420 --> 00:00:34.430 align:start position:0% Italian products and in particular we 00:00:34.430 --> 00:00:36.580 align:start position:0% Italian products and in particular we started<00:00:34.790> with<00:00:34.940> the<00:00:35.090> supply<00:00:35.390> chain<00:00:35.600> ecosystem 00:00:36.580 --> 00:00:36.590 align:start position:0% started with the supply chain ecosystem 00:00:36.590 --> 00:00:40.240 align:start position:0% started with the supply chain ecosystem this<00:00:37.460> project<00:00:37.880> is<00:00:38.000> baked<00:00:38.380> by<00:00:39.380> the<00:00:39.410> Italian 00:00:40.240 --> 00:00:40.250 align:start position:0% this project is baked by the Italian 00:00:40.250 --> 00:00:42.810 align:start position:0% this project is baked by the Italian Ministry<00:00:40.340> of<00:00:40.700> Agriculture 00:00:42.810 --> 00:00:42.820 align:start position:0% Ministry of Agriculture 00:00:42.820 --> 00:00:46.600 align:start position:0% Ministry of Agriculture it's<00:00:43.820> big<00:00:44.060> in<00:00:44.210> complexes<00:00:44.810> so<00:00:45.079> I<00:00:45.470> don't<00:00:46.430> have 00:00:46.600 --> 00:00:46.610 align:start position:0% it's big in complexes so I don't have 00:00:46.610 --> 00:00:49.870 align:start position:0% it's big in complexes so I don't have time<00:00:46.910> to<00:00:47.180> cover<00:00:47.360> all<00:00:47.930> the<00:00:48.170> aspects<00:00:48.700> so<00:00:49.700> in<00:00:49.790> this 00:00:49.870 --> 00:00:49.880 align:start position:0% time to cover all the aspects so in this 00:00:49.880 --> 00:00:53.110 align:start position:0% time to cover all the aspects so in this presentation<00:00:50.030> I<00:00:50.660> summarized<00:00:51.320> them<00:00:51.970> the<00:00:52.970> key 00:00:53.110 --> 00:00:53.120 align:start position:0% presentation I summarized them the key 00:00:53.120 --> 00:00:55.750 align:start position:0% presentation I summarized them the key aspects<00:00:53.510> that<00:00:53.660> I<00:00:53.780> think<00:00:54.160> may<00:00:55.160> help<00:00:55.399> you<00:00:55.550> to 00:00:55.750 --> 00:00:55.760 align:start position:0% aspects that I think may help you to 00:00:55.760 --> 00:00:58.720 align:start position:0% aspects that I think may help you to build<00:00:56.180> a<00:00:56.540> similar<00:00:56.870> solution<00:00:57.430> in<00:00:58.430> other 00:00:58.720 --> 00:00:58.730 align:start position:0% build a similar solution in other 00:00:58.730 --> 00:01:03.610 align:start position:0% build a similar solution in other countries<00:00:59.710> I<00:01:00.710> will<00:01:01.700> happy<00:01:02.000> to<00:01:02.540> answer<00:01:02.870> other 00:01:03.610 --> 00:01:03.620 align:start position:0% countries I will happy to answer other 00:01:03.620 --> 00:01:07.240 align:start position:0% countries I will happy to answer other questions<00:01:04.360> during<00:01:05.360> the<00:01:05.509> break<00:01:05.690> so<00:01:06.680> let's 00:01:07.240 --> 00:01:07.250 align:start position:0% questions during the break so let's 00:01:07.250 --> 00:01:12.190 align:start position:0% questions during the break so let's start<00:01:08.060> from<00:01:08.330> the<00:01:08.420> conclusions<00:01:09.670> I'm<00:01:11.049> this<00:01:12.049> is 00:01:12.190 --> 00:01:12.200 align:start position:0% start from the conclusions I'm this is 00:01:12.200 --> 00:01:14.320 align:start position:0% start from the conclusions I'm this is suggestion<00:01:12.710> from<00:01:12.950> me<00:01:13.220> I<00:01:13.400> am<00:01:13.580> in<00:01:13.670> developer<00:01:14.120> I'm 00:01:14.320 --> 00:01:14.330 align:start position:0% suggestion from me I am in developer I'm 00:01:14.330 --> 00:01:16.410 align:start position:0% suggestion from me I am in developer I'm a<00:01:14.420> solution<00:01:14.780> architect<00:01:14.870> and<00:01:15.380> head<00:01:15.890> of<00:01:16.070> the 00:01:16.410 --> 00:01:16.420 align:start position:0% a solution architect and head of the 00:01:16.420 --> 00:01:19.719 align:start position:0% a solution architect and head of the blockchain<00:01:17.500> competence<00:01:18.500> center<00:01:18.830> in<00:01:19.220> amoeba 00:01:19.719 --> 00:01:19.729 align:start position:0% blockchain competence center in amoeba 00:01:19.729 --> 00:01:23.920 align:start position:0% blockchain competence center in amoeba so<00:01:21.040> let's<00:01:22.040> go<00:01:22.159> fast<00:01:22.400> supply<00:01:23.240> chain<00:01:23.479> exists 00:01:23.920 --> 00:01:23.930 align:start position:0% so let's go fast supply chain exists 00:01:23.930 --> 00:01:27.130 align:start position:0% so let's go fast supply chain exists regardless<00:01:24.530> of<00:01:24.830> IT<00:01:25.250> solutions<00:01:25.520> so<00:01:26.479> you<00:01:26.780> must 00:01:27.130 --> 00:01:27.140 align:start position:0% regardless of IT solutions so you must 00:01:27.140 --> 00:01:31.120 align:start position:0% regardless of IT solutions so you must fit<00:01:28.070> their<00:01:28.970> process<00:01:29.360> no<00:01:29.720> you<00:01:30.049> not<00:01:30.979> the 00:01:31.120 --> 00:01:31.130 align:start position:0% fit their process no you not the 00:01:31.130 --> 00:01:32.109 align:start position:0% fit their process no you not the contrary<00:01:31.520> okay 00:01:32.109 --> 00:01:32.119 align:start position:0% contrary okay 00:01:32.119 --> 00:01:37.149 align:start position:0% contrary okay so<00:01:32.630> you<00:01:34.570> will<00:01:35.570> have<00:01:35.659> submission<00:01:36.380> that<00:01:36.770> evolves 00:01:37.149 --> 00:01:37.159 align:start position:0% so you will have submission that evolves 00:01:37.159 --> 00:01:38.880 align:start position:0% so you will have submission that evolves with<00:01:37.340> business<00:01:37.700> leveraging<00:01:38.330> the<00:01:38.570> technology 00:01:38.880 --> 00:01:38.890 align:start position:0% with business leveraging the technology 00:01:38.890 --> 00:01:42.730 align:start position:0% with business leveraging the technology so<00:01:39.890> don't<00:01:40.369> be<00:01:40.580> a<00:01:40.820> blockchain<00:01:41.240> zealot<00:01:41.740> you 00:01:42.730 --> 00:01:42.740 align:start position:0% so don't be a blockchain zealot you 00:01:42.740 --> 00:01:45.100 align:start position:0% so don't be a blockchain zealot you cannot<00:01:43.100> expect<00:01:43.430> the<00:01:43.640> clients<00:01:44.090> want<00:01:44.750> to<00:01:44.990> know 00:01:45.100 --> 00:01:45.110 align:start position:0% cannot expect the clients want to know 00:01:45.110 --> 00:01:46.570 align:start position:0% cannot expect the clients want to know details<00:01:45.290> of<00:01:45.680> your<00:01:45.830> solution<00:01:46.280> or<00:01:46.460> is 00:01:46.570 --> 00:01:46.580 align:start position:0% details of your solution or is 00:01:46.580 --> 00:01:49.899 align:start position:0% details of your solution or is interesting<00:01:47.090> in<00:01:47.299> how<00:01:47.570> disruptive<00:01:48.820> for<00:01:49.820> the 00:01:49.899 --> 00:01:49.909 align:start position:0% interesting in how disruptive for the 00:01:49.909 --> 00:01:53.350 align:start position:0% interesting in how disruptive for the classical<00:01:50.270> 80<00:01:50.540> world<00:01:50.780> it<00:01:50.960> is<00:01:51.700> each<00:01:52.700> actor<00:01:53.090> of 00:01:53.350 --> 00:01:53.360 align:start position:0% classical 80 world it is each actor of 00:01:53.360 --> 00:01:54.940 align:start position:0% classical 80 world it is each actor of the<00:01:53.479> supply<00:01:53.720> chain<00:01:53.750> as<00:01:54.140> its<00:01:54.350> own<00:01:54.500> expertise 00:01:54.940 --> 00:01:54.950 align:start position:0% the supply chain as its own expertise 00:01:54.950 --> 00:01:57.429 align:start position:0% the supply chain as its own expertise vision<00:01:55.310> business<00:01:55.700> models<00:01:56.479> and<00:01:56.630> goals<00:01:56.930> so<00:01:57.409> you 00:01:57.429 --> 00:01:57.439 align:start position:0% vision business models and goals so you 00:01:57.439 --> 00:02:00.429 align:start position:0% vision business models and goals so you cannot<00:01:57.950> convince<00:01:58.280> them<00:01:58.720> all<00:01:59.720> this<00:02:00.320> the 00:02:00.429 --> 00:02:00.439 align:start position:0% cannot convince them all this the 00:02:00.439 --> 00:02:03.670 align:start position:0% cannot convince them all this the culture<00:02:00.710> to<00:02:00.829> converge<00:02:01.250> to<00:02:01.430> a<00:02:01.490> single<00:02:01.820> goal<00:02:02.000> ok 00:02:03.670 --> 00:02:03.680 align:start position:0% culture to converge to a single goal ok 00:02:03.680 --> 00:02:05.170 align:start position:0% culture to converge to a single goal ok creating<00:02:04.250> an<00:02:04.340> integration<00:02:04.759> or<00:02:04.850> supply<00:02:05.150> chain 00:02:05.170 --> 00:02:05.180 align:start position:0% creating an integration or supply chain 00:02:05.180 --> 00:02:07.450 align:start position:0% creating an integration or supply chain because<00:02:05.450> it<00:02:05.659> is<00:02:05.930> a<00:02:05.960> matter<00:02:06.290> of<00:02:06.409> business<00:02:06.799> not 00:02:07.450 --> 00:02:07.460 align:start position:0% because it is a matter of business not 00:02:07.460 --> 00:02:10.660 align:start position:0% because it is a matter of business not technology<00:02:07.729> so<00:02:08.659> stickers<00:02:08.959> I<00:02:09.079> want<00:02:09.229> to<00:02:09.409> only<00:02:10.369> do 00:02:10.660 --> 00:02:10.670 align:start position:0% technology so stickers I want to only do 00:02:10.670 --> 00:02:14.590 align:start position:0% technology so stickers I want to only do its<00:02:11.420> own<00:02:11.599> job<00:02:12.430> not<00:02:13.430> to<00:02:13.459> be<00:02:13.610> IT<00:02:14.000> expert 00:02:14.590 --> 00:02:14.600 align:start position:0% its own job not to be IT expert 00:02:14.600 --> 00:02:16.960 align:start position:0% its own job not to be IT expert and<00:02:14.690> Sakura<00:02:15.200> used<00:02:15.560> this<00:02:15.820> technology<00:02:16.820> that 00:02:16.960 --> 00:02:16.970 align:start position:0% and Sakura used this technology that 00:02:16.970 --> 00:02:19.480 align:start position:0% and Sakura used this technology that gives<00:02:17.360> them<00:02:17.720> minor<00:02:18.410> cause<00:02:18.710> and<00:02:19.130> better 00:02:19.480 --> 00:02:19.490 align:start position:0% gives them minor cause and better 00:02:19.490 --> 00:02:22.750 align:start position:0% gives them minor cause and better results<00:02:20.110> so<00:02:21.110> what<00:02:21.560> you<00:02:21.710> need<00:02:21.800> to<00:02:21.860> do<00:02:22.040> is<00:02:22.160> find 00:02:22.750 --> 00:02:22.760 align:start position:0% results so what you need to do is find 00:02:22.760 --> 00:02:25.840 align:start position:0% results so what you need to do is find the<00:02:22.880> scenarios<00:02:23.390> that<00:02:23.690> really<00:02:24.530> need<00:02:24.850> addison 00:02:25.840 --> 00:02:25.850 align:start position:0% the scenarios that really need addison 00:02:25.850 --> 00:02:28.270 align:start position:0% the scenarios that really need addison tries<00:02:26.150> the<00:02:26.300> co<00:02:26.420> system<00:02:26.840> so<00:02:27.410> you<00:02:27.950> need<00:02:28.160> to 00:02:28.270 --> 00:02:28.280 align:start position:0% tries the co system so you need to 00:02:28.280 --> 00:02:30.190 align:start position:0% tries the co system so you need to search<00:02:28.490> for<00:02:28.520> a<00:02:28.970> tech<00:02:29.270> genius<00:02:29.450> stake<00:02:29.840> holder 00:02:30.190 --> 00:02:30.200 align:start position:0% search for a tech genius stake holder 00:02:30.200 --> 00:02:33.880 align:start position:0% search for a tech genius stake holder with<00:02:30.410> different<00:02:31.330> goals<00:02:32.330> so<00:02:33.290> for<00:02:33.440> example<00:02:33.830> a 00:02:33.880 --> 00:02:33.890 align:start position:0% with different goals so for example a 00:02:33.890 --> 00:02:37.720 align:start position:0% with different goals so for example a big<00:02:34.130> company<00:02:34.610> with<00:02:35.230> many<00:02:36.230> suppliers<00:02:36.650> it's<00:02:37.460> not 00:02:37.720 --> 00:02:37.730 align:start position:0% big company with many suppliers it's not 00:02:37.730 --> 00:02:41.920 align:start position:0% big company with many suppliers it's not a<00:02:37.760> good<00:02:38.060> idea<00:02:38.770> many<00:02:39.770> intermediaries<00:02:40.490> so<00:02:41.120> if 00:02:41.920 --> 00:02:41.930 align:start position:0% a good idea many intermediaries so if 00:02:41.930 --> 00:02:43.930 align:start position:0% a good idea many intermediaries so if you<00:02:42.170> are<00:02:42.320> in<00:02:42.680> Italy<00:02:42.830> it's<00:02:43.220> a<00:02:43.400> good<00:02:43.610> place<00:02:43.820> to 00:02:43.930 --> 00:02:43.940 align:start position:0% you are in Italy it's a good place to 00:02:43.940 --> 00:02:46.350 align:start position:0% you are in Italy it's a good place to start<00:02:44.210> from<00:02:44.540> and<00:02:45.260> a<00:02:45.470> lot<00:02:45.650> of<00:02:45.680> bureaucracy 00:02:46.350 --> 00:02:46.360 align:start position:0% start from and a lot of bureaucracy 00:02:46.360 --> 00:02:48.580 align:start position:0% start from and a lot of bureaucracy Italy<00:02:47.360> also<00:02:47.480> a<00:02:47.630> good<00:02:47.720> place<00:02:47.990> to<00:02:48.170> start<00:02:48.380> from 00:02:48.580 --> 00:02:48.590 align:start position:0% Italy also a good place to start from 00:02:48.590 --> 00:02:52.450 align:start position:0% Italy also a good place to start from and<00:02:49.060> EU<00:02:50.060> also<00:02:50.920> let's<00:02:51.920> continue<00:02:52.220> the 00:02:52.450 --> 00:02:52.460 align:start position:0% and EU also let's continue the 00:02:52.460 --> 00:02:54.850 align:start position:0% and EU also let's continue the conclusion<00:02:52.970> so<00:02:53.360> you<00:02:53.450> cannot<00:02:53.840> force<00:02:54.170> a<00:02:54.380> supply 00:02:54.850 --> 00:02:54.860 align:start position:0% conclusion so you cannot force a supply 00:02:54.860 --> 00:02:56.650 align:start position:0% conclusion so you cannot force a supply chain<00:02:55.220> ecosystem<00:02:56.030> you<00:02:56.090> need<00:02:56.240> to<00:02:56.330> create<00:02:56.630> a 00:02:56.650 --> 00:02:56.660 align:start position:0% chain ecosystem you need to create a 00:02:56.660 --> 00:02:59.590 align:start position:0% chain ecosystem you need to create a problem<00:02:57.050> my<00:02:57.590> opinion<00:02:57.980> I<00:02:58.070> create<00:02:58.430> a<00:02:58.880> promise' 00:02:59.590 --> 00:02:59.600 align:start position:0% problem my opinion I create a promise' 00:02:59.600 --> 00:03:01.960 align:start position:0% problem my opinion I create a promise' environment<00:03:00.170> that<00:03:00.680> all<00:03:00.890> actor<00:03:01.310> wants<00:03:01.700> to<00:03:01.820> use 00:03:01.960 --> 00:03:01.970 align:start position:0% environment that all actor wants to use 00:03:01.970 --> 00:03:04.900 align:start position:0% environment that all actor wants to use so<00:03:02.930> you<00:03:03.170> create<00:03:03.560> a<00:03:03.620> virtuous<00:03:04.070> cycle<00:03:04.250> that 00:03:04.900 --> 00:03:04.910 align:start position:0% so you create a virtuous cycle that 00:03:04.910 --> 00:03:07.180 align:start position:0% so you create a virtuous cycle that makes<00:03:05.120> other<00:03:05.360> stakeholders<00:03:05.870> to<00:03:05.900> join<00:03:06.140> what<00:03:06.980> is 00:03:07.180 --> 00:03:07.190 align:start position:0% makes other stakeholders to join what is 00:03:07.190 --> 00:03:10.570 align:start position:0% makes other stakeholders to join what is a<00:03:07.220> promisor<00:03:07.720> environment<00:03:08.860> so<00:03:09.860> it<00:03:10.010> fixes<00:03:10.370> some 00:03:10.570 --> 00:03:10.580 align:start position:0% a promisor environment so it fixes some 00:03:10.580 --> 00:03:12.160 align:start position:0% a promisor environment so it fixes some issues<00:03:10.910> from<00:03:11.090> the<00:03:11.270> beginning<00:03:11.630> let's<00:03:12.020> from 00:03:12.160 --> 00:03:12.170 align:start position:0% issues from the beginning let's from 00:03:12.170 --> 00:03:16.360 align:start position:0% issues from the beginning let's from some<00:03:12.620> actor<00:03:13.030> it<00:03:14.030> can<00:03:14.240> grow<00:03:14.530> without<00:03:15.530> relying 00:03:16.360 --> 00:03:16.370 align:start position:0% some actor it can grow without relying 00:03:16.370 --> 00:03:18.100 align:start position:0% some actor it can grow without relying on<00:03:16.520> a<00:03:16.580> single<00:03:16.700> actor<00:03:17.180> and<00:03:17.480> every<00:03:17.720> actor<00:03:17.930> can 00:03:18.100 --> 00:03:18.110 align:start position:0% on a single actor and every actor can 00:03:18.110 --> 00:03:20.620 align:start position:0% on a single actor and every actor can implement<00:03:18.440> new<00:03:18.680> features<00:03:19.450> it<00:03:20.450> has<00:03:20.600> a 00:03:20.620 --> 00:03:20.630 align:start position:0% implement new features it has a 00:03:20.630 --> 00:03:23.500 align:start position:0% implement new features it has a reputational<00:03:21.230> system<00:03:21.620> that<00:03:21.890> emerges<00:03:22.510> during 00:03:23.500 --> 00:03:23.510 align:start position:0% reputational system that emerges during 00:03:23.510 --> 00:03:25.870 align:start position:0% reputational system that emerges during the<00:03:23.600> normal<00:03:23.870> use<00:03:23.990> of<00:03:24.020> the<00:03:24.290> environment<00:03:24.880> by 00:03:25.870 --> 00:03:25.880 align:start position:0% the normal use of the environment by 00:03:25.880 --> 00:03:28.930 align:start position:0% the normal use of the environment by this<00:03:25.940> decoder<00:03:26.510> so<00:03:27.370> endorsing<00:03:28.370> should<00:03:28.580> not<00:03:28.730> be 00:03:28.930 --> 00:03:28.940 align:start position:0% this decoder so endorsing should not be 00:03:28.940 --> 00:03:33.790 align:start position:0% this decoder so endorsing should not be separated<00:03:29.300> step<00:03:30.730> it<00:03:31.730> you<00:03:31.880> should<00:03:32.030> not<00:03:32.180> and<00:03:32.840> at 00:03:33.790 --> 00:03:33.800 align:start position:0% separated step it you should not and at 00:03:33.800 --> 00:03:35.170 align:start position:0% separated step it you should not and at the<00:03:33.950> other<00:03:34.100> step<00:03:34.460> to<00:03:34.610> the<00:03:34.700> stakeholder 00:03:35.170 --> 00:03:35.180 align:start position:0% the other step to the stakeholder 00:03:35.180 --> 00:03:39.790 align:start position:0% the other step to the stakeholder business<00:03:35.480> process<00:03:38.380> providing<00:03:39.380> environment 00:03:39.790 --> 00:03:39.800 align:start position:0% business process providing environment 00:03:39.800 --> 00:03:43.390 align:start position:0% business process providing environment must<00:03:40.190> be<00:03:40.540> massive<00:03:41.540> private<00:03:42.290> investments<00:03:42.860> that 00:03:43.390 --> 00:03:43.400 align:start position:0% must be massive private investments that 00:03:43.400 --> 00:03:46.600 align:start position:0% must be massive private investments that are<00:03:44.120> made<00:03:44.480> to<00:03:44.900> create<00:03:45.410> as<00:03:45.560> they<00:03:45.770> call<00:03:45.950> their<00:03:46.100> IT 00:03:46.600 --> 00:03:46.610 align:start position:0% are made to create as they call their IT 00:03:46.610 --> 00:03:49.390 align:start position:0% are made to create as they call their IT systems<00:03:47.060> and<00:03:47.380> it<00:03:48.380> should<00:03:48.560> be<00:03:48.680> cheaper<00:03:49.160> than 00:03:49.390 --> 00:03:49.400 align:start position:0% systems and it should be cheaper than 00:03:49.400 --> 00:03:52.180 align:start position:0% systems and it should be cheaper than existing<00:03:50.180> solutions<00:03:50.630> or<00:03:50.870> at<00:03:51.170> least<00:03:51.380> and<00:03:52.010> at 00:03:52.180 --> 00:03:52.190 align:start position:0% existing solutions or at least and at 00:03:52.190 --> 00:03:55.050 align:start position:0% existing solutions or at least and at least<00:03:52.880> the<00:03:53.060> same<00:03:53.270> the<00:03:53.960> same<00:03:54.110> features 00:03:55.050 --> 00:03:55.060 align:start position:0% least the same the same features 00:03:55.060 --> 00:03:59.200 align:start position:0% least the same the same features stakeholders<00:03:56.060> can<00:03:56.330> live<00:03:57.230> and<00:03:57.800> must<00:03:58.490> can<00:03:59.000> live 00:03:59.200 --> 00:03:59.210 align:start position:0% stakeholders can live and must can live 00:03:59.210 --> 00:04:03.100 align:start position:0% stakeholders can live and must can live enjoy<00:04:00.370> the<00:04:01.540> ecosystem<00:04:02.540> whatever<00:04:02.780> they<00:04:02.900> want 00:04:03.100 --> 00:04:03.110 align:start position:0% enjoy the ecosystem whatever they want 00:04:03.110 --> 00:04:06.030 align:start position:0% enjoy the ecosystem whatever they want without<00:04:03.500> shame<00:04:03.890> and<00:04:04.190> justification<00:04:04.880> and 00:04:06.030 --> 00:04:06.040 align:start position:0% without shame and justification and 00:04:06.040 --> 00:04:08.800 align:start position:0% without shame and justification and regulators<00:04:07.060> must<00:04:08.060> recognize<00:04:08.600> and 00:04:08.800 --> 00:04:08.810 align:start position:0% regulators must recognize and 00:04:08.810 --> 00:04:10.450 align:start position:0% regulators must recognize and participate<00:04:09.230> in<00:04:09.350> the<00:04:09.410> environment<00:04:09.830> really 00:04:10.450 --> 00:04:10.460 align:start position:0% participate in the environment really 00:04:10.460 --> 00:04:16.000 align:start position:0% participate in the environment really important<00:04:10.940> bold<00:04:11.210> underlined<00:04:12.970> so<00:04:15.010> private 00:04:16.000 --> 00:04:16.010 align:start position:0% important bold underlined so private 00:04:16.010 --> 00:04:19.140 align:start position:0% important bold underlined so private companies<00:04:16.400> look<00:04:17.359> for<00:04:17.530> retro<00:04:18.530> investment 00:04:19.140 --> 00:04:19.150 align:start position:0% companies look for retro investment 00:04:19.150 --> 00:04:22.000 align:start position:0% companies look for retro investment sooner<00:04:20.150> the<00:04:20.299> better<00:04:20.420> they<00:04:21.080> never<00:04:21.350> really<00:04:21.859> do 00:04:22.000 --> 00:04:22.010 align:start position:0% sooner the better they never really do 00:04:22.010 --> 00:04:24.390 align:start position:0% sooner the better they never really do charity<00:04:22.550> so<00:04:22.880> I<00:04:23.120> think<00:04:23.330> that<00:04:23.750> your<00:04:23.870> company 00:04:24.390 --> 00:04:24.400 align:start position:0% charity so I think that your company 00:04:24.400 --> 00:04:26.540 align:start position:0% charity so I think that your company does<00:04:25.400> not<00:04:25.430> exception<00:04:26.090> so 00:04:26.540 --> 00:04:26.550 align:start position:0% does not exception so 00:04:26.550 --> 00:04:29.210 align:start position:0% does not exception so you<00:04:27.180> I<00:04:27.509> suggest<00:04:28.080> to<00:04:28.409> stick<00:04:28.650> close<00:04:28.680> to 00:04:29.210 --> 00:04:29.220 align:start position:0% you I suggest to stick close to 00:04:29.220 --> 00:04:31.909 align:start position:0% you I suggest to stick close to government<00:04:29.430> organization<00:04:30.389> they<00:04:30.569> can<00:04:30.919> really 00:04:31.909 --> 00:04:31.919 align:start position:0% government organization they can really 00:04:31.919 --> 00:04:33.950 align:start position:0% government organization they can really boost<00:04:32.039> the<00:04:32.310> creation<00:04:32.819> of<00:04:33.030> the<00:04:33.539> environment 00:04:33.950 --> 00:04:33.960 align:start position:0% boost the creation of the environment 00:04:33.960 --> 00:04:36.920 align:start position:0% boost the creation of the environment because<00:04:34.919> they<00:04:35.039> can<00:04:35.190> spend<00:04:35.400> money<00:04:35.520> for<00:04:35.879> go<00:04:36.690> of 00:04:36.920 --> 00:04:36.930 align:start position:0% because they can spend money for go of 00:04:36.930 --> 00:04:40.249 align:start position:0% because they can spend money for go of the<00:04:37.139> community<00:04:37.590> and<00:04:38.030> this<00:04:39.030> is<00:04:39.419> exactly<00:04:39.840> their 00:04:40.249 --> 00:04:40.259 align:start position:0% the community and this is exactly their 00:04:40.259 --> 00:04:44.149 align:start position:0% the community and this is exactly their own<00:04:40.500> return<00:04:41.190> on<00:04:41.340> investment<00:04:41.900> and<00:04:43.159> we 00:04:44.149 --> 00:04:44.159 align:start position:0% own return on investment and we 00:04:44.159 --> 00:04:47.689 align:start position:0% own return on investment and we conclusion<00:04:44.669> you<00:04:44.970> need<00:04:45.180> the<00:04:45.810> regulator's<00:04:46.699> to 00:04:47.689 --> 00:04:47.699 align:start position:0% conclusion you need the regulator's to 00:04:47.699 --> 00:04:50.330 align:start position:0% conclusion you need the regulator's to get<00:04:47.909> rid<00:04:48.090> of<00:04:48.120> regulation<00:04:48.840> so<00:04:49.139> don't<00:04:49.710> try<00:04:49.949> to<00:04:50.009> be 00:04:50.330 --> 00:04:50.340 align:start position:0% get rid of regulation so don't try to be 00:04:50.340 --> 00:04:51.860 align:start position:0% get rid of regulation so don't try to be the<00:04:50.370> new<00:04:50.580> regulators<00:04:51.090> just<00:04:51.479> because<00:04:51.720> you 00:04:51.860 --> 00:04:51.870 align:start position:0% the new regulators just because you 00:04:51.870 --> 00:04:55.040 align:start position:0% the new regulators just because you master<00:04:52.530> the<00:04:52.770> blockchain<00:04:53.159> and<00:04:53.449> you<00:04:54.449> need<00:04:54.599> the 00:04:55.040 --> 00:04:55.050 align:start position:0% master the blockchain and you need the 00:04:55.050 --> 00:04:57.010 align:start position:0% master the blockchain and you need the materialization<00:04:55.590> really<00:04:56.250> really<00:04:56.759> much 00:04:57.010 --> 00:04:57.020 align:start position:0% materialization really really much 00:04:57.020 --> 00:05:00.499 align:start position:0% materialization really really much damage<00:04:58.020> organization<00:04:58.909> start<00:04:59.909> creating<00:05:00.240> a 00:05:00.499 --> 00:05:00.509 align:start position:0% damage organization start creating a 00:05:00.509 --> 00:05:02.779 align:start position:0% damage organization start creating a decentralized<00:05:01.110> solution<00:05:01.560> that<00:05:01.979> simply<00:05:02.550> works 00:05:02.779 --> 00:05:02.789 align:start position:0% decentralized solution that simply works 00:05:02.789 --> 00:05:05.869 align:start position:0% decentralized solution that simply works don't<00:05:03.210> try<00:05:03.840> to<00:05:03.900> build<00:05:04.469> a<00:05:04.770> complete<00:05:05.370> solution 00:05:05.869 --> 00:05:05.879 align:start position:0% don't try to build a complete solution 00:05:05.879 --> 00:05:08.600 align:start position:0% don't try to build a complete solution from<00:05:06.360> the<00:05:06.539> start<00:05:06.780> so<00:05:07.379> you<00:05:07.620> cannot<00:05:07.860> force<00:05:08.250> the 00:05:08.600 --> 00:05:08.610 align:start position:0% from the start so you cannot force the 00:05:08.610 --> 00:05:10.670 align:start position:0% from the start so you cannot force the use<00:05:08.729> of<00:05:08.879> specific<00:05:09.090> IT<00:05:09.569> supply<00:05:10.080> chain<00:05:10.229> solution 00:05:10.670 --> 00:05:10.680 align:start position:0% use of specific IT supply chain solution 00:05:10.680 --> 00:05:13.879 align:start position:0% use of specific IT supply chain solution because<00:05:11.550> it<00:05:11.669> never<00:05:11.879> fits<00:05:12.469> the<00:05:13.469> needs<00:05:13.650> of<00:05:13.740> all 00:05:13.879 --> 00:05:13.889 align:start position:0% because it never fits the needs of all 00:05:13.889 --> 00:05:18.469 align:start position:0% because it never fits the needs of all stakeholder<00:05:14.690> in<00:05:15.690> any<00:05:15.870> case<00:05:16.580> there<00:05:17.580> there's<00:05:18.360> no 00:05:18.469 --> 00:05:18.479 align:start position:0% stakeholder in any case there there's no 00:05:18.479 --> 00:05:19.580 align:start position:0% stakeholder in any case there there's no single<00:05:18.780> solution<00:05:19.080> that<00:05:19.199> rule<00:05:19.349> them<00:05:19.500> all 00:05:19.580 --> 00:05:19.590 align:start position:0% single solution that rule them all 00:05:19.590 --> 00:05:22.159 align:start position:0% single solution that rule them all there's<00:05:20.190> no<00:05:20.370> single<00:05:21.120> smart<00:05:21.330> contractors<00:05:21.930> rule 00:05:22.159 --> 00:05:22.169 align:start position:0% there's no single smart contractors rule 00:05:22.169 --> 00:05:22.670 align:start position:0% there's no single smart contractors rule them<00:05:22.349> all 00:05:22.670 --> 00:05:22.680 align:start position:0% them all 00:05:22.680 --> 00:05:25.719 align:start position:0% them all so<00:05:23.069> it's<00:05:23.340> always<00:05:23.550> a<00:05:23.819> matter<00:05:24.000> of<00:05:24.180> integration 00:05:25.719 --> 00:05:25.729 align:start position:0% so it's always a matter of integration 00:05:25.729 --> 00:05:28.189 align:start position:0% so it's always a matter of integration please<00:05:26.729> use<00:05:26.940> the<00:05:27.210> blockchain<00:05:27.419> for<00:05:27.780> what<00:05:27.930> it<00:05:28.169> is 00:05:28.189 --> 00:05:28.199 align:start position:0% please use the blockchain for what it is 00:05:28.199 --> 00:05:31.790 align:start position:0% please use the blockchain for what it is better<00:05:28.770> so<00:05:30.020> leveraging<00:05:31.020> all<00:05:31.229> the 00:05:31.790 --> 00:05:31.800 align:start position:0% better so leveraging all the 00:05:31.800 --> 00:05:33.890 align:start position:0% better so leveraging all the peer-to-peer<00:05:32.219> technology<00:05:32.819> and<00:05:33.029> integrate 00:05:33.890 --> 00:05:33.900 align:start position:0% peer-to-peer technology and integrate 00:05:33.900 --> 00:05:35.719 align:start position:0% peer-to-peer technology and integrate those<00:05:34.110> technology<00:05:34.710> with<00:05:34.860> legacy<00:05:35.250> system<00:05:35.580> we 00:05:35.719 --> 00:05:35.729 align:start position:0% those technology with legacy system we 00:05:35.729 --> 00:05:39.309 align:start position:0% those technology with legacy system we need<00:05:35.880> legacy<00:05:36.509> system<00:05:36.840> for<00:05:37.110> many<00:05:37.830> years<00:05:38.159> I<00:05:38.580> go 00:05:39.309 --> 00:05:39.319 align:start position:0% need legacy system for many years I go 00:05:39.319 --> 00:05:43.040 align:start position:0% need legacy system for many years I go more<00:05:40.319> and<00:05:40.759> again<00:05:41.759> you<00:05:41.940> don't<00:05:42.180> need<00:05:42.389> to<00:05:42.690> do<00:05:42.810> all 00:05:43.040 --> 00:05:43.050 align:start position:0% more and again you don't need to do all 00:05:43.050 --> 00:05:46.490 align:start position:0% more and again you don't need to do all on<00:05:43.560> the<00:05:44.069> blockchain<00:05:44.279> really<00:05:44.789> you<00:05:45.000> need<00:05:45.719> so 00:05:46.490 --> 00:05:46.500 align:start position:0% on the blockchain really you need so 00:05:46.500 --> 00:05:47.300 align:start position:0% on the blockchain really you need so don't<00:05:46.740> do<00:05:46.889> it 00:05:47.300 --> 00:05:47.310 align:start position:0% don't do it 00:05:47.310 --> 00:05:49.279 align:start position:0% don't do it start<00:05:47.789> with<00:05:47.969> solution<00:05:48.479> integration<00:05:48.960> features 00:05:49.279 --> 00:05:49.289 align:start position:0% start with solution integration features 00:05:49.289 --> 00:05:51.170 align:start position:0% start with solution integration features the<00:05:49.380> prepare<00:05:49.979> the<00:05:50.159> environment<00:05:50.580> for<00:05:50.880> the<00:05:51.029> grow 00:05:51.170 --> 00:05:51.180 align:start position:0% the prepare the environment for the grow 00:05:51.180 --> 00:05:53.779 align:start position:0% the prepare the environment for the grow of<00:05:51.360> the<00:05:51.479> ecosystem<00:05:51.990> ok<00:05:52.500> so<00:05:52.860> if<00:05:53.310> you<00:05:53.370> follow 00:05:53.779 --> 00:05:53.789 align:start position:0% of the ecosystem ok so if you follow 00:05:53.789 --> 00:05:57.260 align:start position:0% of the ecosystem ok so if you follow these<00:05:54.029> rules<00:05:54.090> I<00:05:54.449> think<00:05:54.479> you<00:05:54.990> can<00:05:55.879> use<00:05:56.879> a<00:05:57.090> theory 00:05:57.260 --> 00:05:57.270 align:start position:0% these rules I think you can use a theory 00:05:57.270 --> 00:05:59.629 align:start position:0% these rules I think you can use a theory of<00:05:57.360> Manor<00:05:57.770> for<00:05:58.770> a<00:05:58.800> builder 00:05:59.629 --> 00:05:59.639 align:start position:0% of Manor for a builder 00:05:59.639 --> 00:06:01.219 align:start position:0% of Manor for a builder decentralized<00:06:00.120> supply<00:06:00.539> chain<00:06:00.690> solution<00:06:01.080> and 00:06:01.219 --> 00:06:01.229 align:start position:0% decentralized supply chain solution and 00:06:01.229 --> 00:06:04.670 align:start position:0% decentralized supply chain solution and you<00:06:01.289> can<00:06:01.440> build<00:06:01.590> it<00:06:01.800> now<00:06:02.990> just<00:06:03.990> gather<00:06:04.229> with 00:06:04.670 --> 00:06:04.680 align:start position:0% you can build it now just gather with 00:06:04.680 --> 00:06:07.159 align:start position:0% you can build it now just gather with others<00:06:05.099> don't<00:06:05.699> try<00:06:05.909> this<00:06:05.969> at<00:06:06.120> all<00:06:06.389> alone<00:06:06.840> and 00:06:07.159 --> 00:06:07.169 align:start position:0% others don't try this at all alone and 00:06:07.169 --> 00:06:09.920 align:start position:0% others don't try this at all alone and if<00:06:07.620> you<00:06:07.650> want<00:06:07.940> you<00:06:08.940> can<00:06:09.060> start<00:06:09.449> building<00:06:09.629> with 00:06:09.920 --> 00:06:09.930 align:start position:0% if you want you can start building with 00:06:09.930 --> 00:06:14.839 align:start position:0% if you want you can start building with us<00:06:10.219> so<00:06:11.219> when<00:06:11.669> I<00:06:11.819> who<00:06:12.599> we<00:06:12.779> are<00:06:12.930> we<00:06:13.259> are<00:06:13.669> quite<00:06:14.669> big 00:06:14.839 --> 00:06:14.849 align:start position:0% us so when I who we are we are quite big 00:06:14.849 --> 00:06:18.170 align:start position:0% us so when I who we are we are quite big company<00:06:15.949> so<00:06:16.949> we<00:06:17.219> are<00:06:17.340> in<00:06:17.520> all<00:06:17.759> over<00:06:17.940> the<00:06:18.060> world 00:06:18.170 --> 00:06:18.180 align:start position:0% company so we are in all over the world 00:06:18.180 --> 00:06:20.930 align:start position:0% company so we are in all over the world Italy<00:06:18.840> Brazil<00:06:19.050> United<00:06:19.500> staes<00:06:19.889> we<00:06:20.129> have<00:06:20.279> many 00:06:20.930 --> 00:06:20.940 align:start position:0% Italy Brazil United staes we have many 00:06:20.940 --> 00:06:23.570 align:start position:0% Italy Brazil United staes we have many many<00:06:21.150> people<00:06:21.210> that<00:06:21.599> works<00:06:21.960> with<00:06:22.169> us<00:06:22.349> and<00:06:23.129> we 00:06:23.570 --> 00:06:23.580 align:start position:0% many people that works with us and we 00:06:23.580 --> 00:06:26.390 align:start position:0% many people that works with us and we cover<00:06:23.789> all<00:06:24.120> these<00:06:24.599> markets<00:06:25.050> so<00:06:25.259> in<00:06:25.919> popular 00:06:26.390 --> 00:06:26.400 align:start position:0% cover all these markets so in popular 00:06:26.400 --> 00:06:28.010 align:start position:0% cover all these markets so in popular public<00:06:26.819> administration<00:06:27.389> teleportation 00:06:28.010 --> 00:06:28.020 align:start position:0% public administration teleportation 00:06:28.020 --> 00:06:31.689 align:start position:0% public administration teleportation energy<00:06:28.319> istic<00:06:28.650> and<00:06:28.830> so<00:06:29.009> on<00:06:29.539> I<00:06:30.539> think<00:06:30.840> you 00:06:31.689 --> 00:06:31.699 align:start position:0% energy istic and so on I think you 00:06:31.699 --> 00:06:35.899 align:start position:0% energy istic and so on I think you understand<00:06:32.699> the<00:06:32.759> kind<00:06:33.210> of<00:06:33.800> love<00:06:34.800> company<00:06:35.339> and 00:06:35.899 --> 00:06:35.909 align:start position:0% understand the kind of love company and 00:06:35.909 --> 00:06:38.420 align:start position:0% understand the kind of love company and we<00:06:36.509> have<00:06:36.630> many<00:06:37.050> partnerships<00:06:37.620> so<00:06:37.919> if<00:06:38.130> you<00:06:38.219> want 00:06:38.420 --> 00:06:38.430 align:start position:0% we have many partnerships so if you want 00:06:38.430 --> 00:06:40.100 align:start position:0% we have many partnerships so if you want to<00:06:38.669> be<00:06:39.000> with<00:06:39.210> us<00:06:39.360> just 00:06:40.100 --> 00:06:40.110 align:start position:0% to be with us just 00:06:40.110 --> 00:06:43.610 align:start position:0% to be with us just say<00:06:40.260> hi<00:06:40.740> and<00:06:41.360> to<00:06:42.360> cover<00:06:42.540> all<00:06:42.840> the<00:06:43.050> aspects<00:06:43.440> of 00:06:43.610 --> 00:06:43.620 align:start position:0% say hi and to cover all the aspects of 00:06:43.620 --> 00:06:45.590 align:start position:0% say hi and to cover all the aspects of the<00:06:43.830> new<00:06:44.460> technology<00:06:44.490> we<00:06:45.030> have<00:06:45.300> many 00:06:45.590 --> 00:06:45.600 align:start position:0% the new technology we have many 00:06:45.600 --> 00:06:47.330 align:start position:0% the new technology we have many components<00:06:46.050> Center<00:06:46.410> as<00:06:46.740> well<00:06:46.920> ready<00:06:47.100> said<00:06:47.310> I 00:06:47.330 --> 00:06:47.340 align:start position:0% components Center as well ready said I 00:06:47.340 --> 00:06:50.660 align:start position:0% components Center as well ready said I work<00:06:47.790> with<00:06:48.060> the<00:06:48.320> ml<00:06:49.320> of<00:06:49.370> blockchain<00:06:50.370> command 00:06:50.660 --> 00:06:50.670 align:start position:0% work with the ml of blockchain command 00:06:50.670 --> 00:06:52.460 align:start position:0% work with the ml of blockchain command center<00:06:51.090> and<00:06:51.300> I<00:06:51.540> work<00:06:51.690> with<00:06:51.930> other<00:06:52.080> comes<00:06:52.380> the 00:06:52.460 --> 00:06:52.470 align:start position:0% center and I work with other comes the 00:06:52.470 --> 00:06:54.110 align:start position:0% center and I work with other comes the center<00:06:52.710> to<00:06:52.830> provide<00:06:53.100> this<00:06:53.250> kind<00:06:53.850> of<00:06:53.940> solution 00:06:54.110 --> 00:06:54.120 align:start position:0% center to provide this kind of solution 00:06:54.120 --> 00:06:57.590 align:start position:0% center to provide this kind of solution because<00:06:54.570> it's<00:06:55.200> a<00:06:55.790> need<00:06:56.790> to<00:06:56.910> be<00:06:57.030> many 00:06:57.590 --> 00:06:57.600 align:start position:0% because it's a need to be many 00:06:57.600 --> 00:06:59.960 align:start position:0% because it's a need to be many competences<00:06:58.320> to<00:06:58.590> provide<00:06:59.190> this<00:06:59.550> solution<00:06:59.760> to 00:06:59.960 --> 00:06:59.970 align:start position:0% competences to provide this solution to 00:06:59.970 --> 00:07:03.380 align:start position:0% competences to provide this solution to the<00:07:00.090> customer<00:07:01.010> blockchain<00:07:02.010> is<00:07:02.040> used<00:07:02.370> here<00:07:02.790> as 00:07:03.380 --> 00:07:03.390 align:start position:0% the customer blockchain is used here as 00:07:03.390 --> 00:07:07.330 align:start position:0% the customer blockchain is used here as a<00:07:03.710> keyword<00:07:04.710> as<00:07:05.040> a<00:07:05.070> shortcut<00:07:05.520> because<00:07:05.880> I<00:07:06.330> really 00:07:07.330 --> 00:07:07.340 align:start position:0% a keyword as a shortcut because I really 00:07:07.340 --> 00:07:10.580 align:start position:0% a keyword as a shortcut because I really trust<00:07:08.340> that<00:07:08.550> the<00:07:08.880> focus<00:07:09.810> here<00:07:09.960> is<00:07:10.020> to<00:07:10.380> create 00:07:10.580 --> 00:07:10.590 align:start position:0% trust that the focus here is to create 00:07:10.590 --> 00:07:13.220 align:start position:0% trust that the focus here is to create the<00:07:10.890> centralized<00:07:11.250> solutions<00:07:11.910> so<00:07:12.690> blockchain 00:07:13.220 --> 00:07:13.230 align:start position:0% the centralized solutions so blockchain 00:07:13.230 --> 00:07:15.890 align:start position:0% the centralized solutions so blockchain is<00:07:13.260> the<00:07:13.800> the<00:07:14.760> main<00:07:14.910> technology<00:07:15.660> for<00:07:15.810> this 00:07:15.890 --> 00:07:15.900 align:start position:0% is the the main technology for this 00:07:15.900 --> 00:07:18.830 align:start position:0% is the the main technology for this solution<00:07:16.200> but<00:07:16.530> it's<00:07:16.740> not<00:07:16.980> the<00:07:17.190> only<00:07:17.520> one<00:07:17.840> so 00:07:18.830 --> 00:07:18.840 align:start position:0% solution but it's not the only one so 00:07:18.840 --> 00:07:23.330 align:start position:0% solution but it's not the only one so scenario<00:07:20.420> Italy<00:07:21.420> is<00:07:21.630> one<00:07:21.690> logic<00:07:22.340> agriculture 00:07:23.330 --> 00:07:23.340 align:start position:0% scenario Italy is one logic agriculture 00:07:23.340 --> 00:07:26.540 align:start position:0% scenario Italy is one logic agriculture producer<00:07:23.760> of<00:07:23.910> food<00:07:24.090> and<00:07:24.240> processor<00:07:24.690> in<00:07:24.990> the<00:07:25.550> in 00:07:26.540 --> 00:07:26.550 align:start position:0% producer of food and processor in the in 00:07:26.550 --> 00:07:29.870 align:start position:0% producer of food and processor in the in the<00:07:26.760> European<00:07:27.570> Union<00:07:28.110> there<00:07:28.950> is<00:07:29.010> 1<00:07:29.700> million 00:07:29.870 --> 00:07:29.880 align:start position:0% the European Union there is 1 million 00:07:29.880 --> 00:07:32.360 align:start position:0% the European Union there is 1 million people<00:07:30.470> directly<00:07:31.470> on<00:07:31.590> directly<00:07:31.890> involved<00:07:32.190> in 00:07:32.360 --> 00:07:32.370 align:start position:0% people directly on directly involved in 00:07:32.370 --> 00:07:35.630 align:start position:0% people directly on directly involved in the<00:07:32.940> production<00:07:33.090> chain<00:07:33.420> we<00:07:34.160> created<00:07:35.160> not<00:07:35.400> one 00:07:35.630 --> 00:07:35.640 align:start position:0% the production chain we created not one 00:07:35.640 --> 00:07:39.230 align:start position:0% the production chain we created not one but<00:07:35.880> four<00:07:36.660> marks<00:07:37.530> of<00:07:37.650> guarantee<00:07:38.100> that<00:07:38.310> the 00:07:39.230 --> 00:07:39.240 align:start position:0% but four marks of guarantee that the 00:07:39.240 --> 00:07:40.850 align:start position:0% but four marks of guarantee that the food<00:07:39.420> of<00:07:39.540> wine<00:07:39.720> products<00:07:40.290> tasted<00:07:40.680> as<00:07:40.800> a 00:07:40.850 --> 00:07:40.860 align:start position:0% food of wine products tasted as a 00:07:40.860 --> 00:07:42.170 align:start position:0% food of wine products tasted as a traditional<00:07:41.640> food 00:07:42.170 --> 00:07:42.180 align:start position:0% traditional food 00:07:42.180 --> 00:07:45.260 align:start position:0% traditional food okay<00:07:42.630> so<00:07:42.930> the<00:07:43.350> main<00:07:43.970> architect<00:07:44.970> capture 00:07:45.260 --> 00:07:45.270 align:start position:0% okay so the main architect capture 00:07:45.270 --> 00:07:47.810 align:start position:0% okay so the main architect capture market<00:07:46.050> treat<00:07:46.290> that<00:07:46.920> they<00:07:47.010> want<00:07:47.190> to<00:07:47.250> solve<00:07:47.460> is 00:07:47.810 --> 00:07:47.820 align:start position:0% market treat that they want to solve is 00:07:47.820 --> 00:07:50.870 align:start position:0% market treat that they want to solve is product<00:07:48.630> counter<00:07:48.990> failing<00:07:49.880> national 00:07:50.870 --> 00:07:50.880 align:start position:0% product counter failing national 00:07:50.880 --> 00:07:54.500 align:start position:0% product counter failing national international<00:07:52.100> we<00:07:53.100> choose<00:07:53.940> to<00:07:54.090> start<00:07:54.300> from 00:07:54.500 --> 00:07:54.510 align:start position:0% international we choose to start from 00:07:54.510 --> 00:07:57.080 align:start position:0% international we choose to start from wine<00:07:54.780> because<00:07:55.740> Italy<00:07:56.430> is<00:07:56.460> a<00:07:56.580> larger<00:07:56.940> wine 00:07:57.080 --> 00:07:57.090 align:start position:0% wine because Italy is a larger wine 00:07:57.090 --> 00:07:57.980 align:start position:0% wine because Italy is a larger wine producer<00:07:57.420> in<00:07:57.600> the<00:07:57.690> world 00:07:57.980 --> 00:07:57.990 align:start position:0% producer in the world 00:07:57.990 --> 00:08:02.480 align:start position:0% producer in the world so<00:07:58.410> we<00:07:58.710> produce<00:07:59.960> 500<00:08:00.960> millions<00:08:01.860> of<00:08:02.070> liters<00:08:02.340> of 00:08:02.480 --> 00:08:02.490 align:start position:0% so we produce 500 millions of liters of 00:08:02.490 --> 00:08:05.260 align:start position:0% so we produce 500 millions of liters of wine<00:08:02.610> per<00:08:03.030> year<00:08:03.300> we<00:08:03.960> are<00:08:04.080> very<00:08:04.110> thirsty<00:08:04.530> and 00:08:05.260 --> 00:08:05.270 align:start position:0% wine per year we are very thirsty and 00:08:05.270 --> 00:08:08.840 align:start position:0% wine per year we are very thirsty and the<00:08:06.270> possibility<00:08:06.840> of<00:08:06.990> Italian<00:08:07.500> agri-food<00:08:07.860> is 00:08:08.840 --> 00:08:08.850 align:start position:0% the possibility of Italian agri-food is 00:08:08.850 --> 00:08:11.330 align:start position:0% the possibility of Italian agri-food is the<00:08:09.060> most<00:08:09.270> discussed<00:08:09.600> stopping<00:08:10.080> for<00:08:11.010> benefit 00:08:11.330 --> 00:08:11.340 align:start position:0% the most discussed stopping for benefit 00:08:11.340 --> 00:08:13.070 align:start position:0% the most discussed stopping for benefit it<00:08:11.490> can<00:08:11.640> make<00:08:11.850> in<00:08:12.090> several<00:08:12.420> application<00:08:12.810> areas 00:08:13.070 --> 00:08:13.080 align:start position:0% it can make in several application areas 00:08:13.080 --> 00:08:15.830 align:start position:0% it can make in several application areas so<00:08:13.860> what<00:08:14.400> we<00:08:14.490> need<00:08:14.640> to<00:08:14.970> do<00:08:15.180> to<00:08:15.690> guarantee 00:08:15.830 --> 00:08:15.840 align:start position:0% so what we need to do to guarantee 00:08:15.840 --> 00:08:17.690 align:start position:0% so what we need to do to guarantee quality<00:08:16.380> consumer<00:08:16.980> safety<00:08:17.310> and<00:08:17.400> protection 00:08:17.690 --> 00:08:17.700 align:start position:0% quality consumer safety and protection 00:08:17.700 --> 00:08:19.910 align:start position:0% quality consumer safety and protection of<00:08:17.880> Italian<00:08:18.390> of<00:08:18.900> the<00:08:19.080> middlee<00:08:19.380> project<00:08:19.770> of 00:08:19.910 --> 00:08:19.920 align:start position:0% of Italian of the middlee project of 00:08:19.920 --> 00:08:22.790 align:start position:0% of Italian of the middlee project of made<00:08:20.430> in<00:08:20.580> Italy<00:08:20.880> products<00:08:21.330> sorry<00:08:21.600> and<00:08:22.110> to 00:08:22.790 --> 00:08:22.800 align:start position:0% made in Italy products sorry and to 00:08:22.800 --> 00:08:24.980 align:start position:0% made in Italy products sorry and to determine<00:08:23.130> the<00:08:23.310> origin<00:08:24.210> and<00:08:24.360> characteristics 00:08:24.980 --> 00:08:24.990 align:start position:0% determine the origin and characteristics 00:08:24.990 --> 00:08:27.430 align:start position:0% determine the origin and characteristics that<00:08:25.470> make<00:08:25.860> the<00:08:26.010> products<00:08:26.430> unique 00:08:27.430 --> 00:08:27.440 align:start position:0% that make the products unique 00:08:27.440 --> 00:08:29.840 align:start position:0% that make the products unique traditional<00:08:28.440> tracking<00:08:29.250> meters<00:08:29.490> are<00:08:29.670> not 00:08:29.840 --> 00:08:29.850 align:start position:0% traditional tracking meters are not 00:08:29.850 --> 00:08:31.940 align:start position:0% traditional tracking meters are not enough<00:08:30.120> to<00:08:30.690> contract<00:08:31.110> and<00:08:31.350> discourage 00:08:31.940 --> 00:08:31.950 align:start position:0% enough to contract and discourage 00:08:31.950 --> 00:08:36.620 align:start position:0% enough to contract and discourage counterfeiting<00:08:32.760> phenomenon<00:08:33.350> so<00:08:35.330> the<00:08:36.330> actors 00:08:36.620 --> 00:08:36.630 align:start position:0% counterfeiting phenomenon so the actors 00:08:36.630 --> 00:08:39.500 align:start position:0% counterfeiting phenomenon so the actors involved<00:08:36.870> in<00:08:37.050> this<00:08:37.200> ecosystem<00:08:38.010> are<00:08:38.460> many<00:08:39.030> we 00:08:39.500 --> 00:08:39.510 align:start position:0% involved in this ecosystem are many we 00:08:39.510 --> 00:08:42.860 align:start position:0% involved in this ecosystem are many we hear<00:08:40.500> here<00:08:40.979> you<00:08:41.070> can<00:08:41.250> see<00:08:41.460> the<00:08:42.000> main<00:08:42.180> there<00:08:42.750> are 00:08:42.860 --> 00:08:42.870 align:start position:0% hear here you can see the main there are 00:08:42.870 --> 00:08:45.620 align:start position:0% hear here you can see the main there are producer<00:08:43.260> wireless<00:08:43.860> transporters<00:08:44.670> consumers 00:08:45.620 --> 00:08:45.630 align:start position:0% producer wireless transporters consumers 00:08:45.630 --> 00:08:48.560 align:start position:0% producer wireless transporters consumers association<00:08:45.960> all<00:08:46.700> associations<00:08:47.700> are<00:08:48.300> all 00:08:48.560 --> 00:08:48.570 align:start position:0% association all associations are all 00:08:48.570 --> 00:08:51.170 align:start position:0% association all associations are all these<00:08:49.260> player<00:08:49.980> sources<00:08:50.610> or<00:08:50.730> producers 00:08:51.170 --> 00:08:51.180 align:start position:0% these player sources or producers 00:08:51.180 --> 00:08:52.710 align:start position:0% these player sources or producers wineries<00:08:51.570> and<00:08:51.840> so<00:08:51.960> on<00:08:52.080> model 00:08:52.710 --> 00:08:52.720 align:start position:0% wineries and so on model 00:08:52.720 --> 00:08:55.500 align:start position:0% wineries and so on model göran<00:08:53.560> organization<00:08:54.220> and<00:08:54.460> so<00:08:54.640> on<00:08:54.730> they<00:08:55.480> all 00:08:55.500 --> 00:08:55.510 align:start position:0% göran organization and so on they all 00:08:55.510 --> 00:08:58.680 align:start position:0% göran organization and so on they all share<00:08:56.640> essentially<00:08:57.640> the<00:08:57.760> same<00:08:57.970> issues 00:08:58.680 --> 00:08:58.690 align:start position:0% share essentially the same issues 00:08:58.690 --> 00:09:01.650 align:start position:0% share essentially the same issues militaire<00:08:59.650> documentation<00:09:00.360> intially<00:09:01.360> often 00:09:01.650 --> 00:09:01.660 align:start position:0% militaire documentation intially often 00:09:01.660 --> 00:09:04.560 align:start position:0% militaire documentation intially often is<00:09:02.500> stealing<00:09:02.920> paper<00:09:03.130> and<00:09:03.850> container<00:09:04.420> they 00:09:04.560 --> 00:09:04.570 align:start position:0% is stealing paper and container they 00:09:04.570 --> 00:09:06.270 align:start position:0% is stealing paper and container they don't<00:09:04.750> have<00:09:04.840> information<00:09:05.050> so<00:09:05.740> there<00:09:06.130> is<00:09:06.250> a 00:09:06.270 --> 00:09:06.280 align:start position:0% don't have information so there is a 00:09:06.280 --> 00:09:08.940 align:start position:0% don't have information so there is a delay<00:09:07.000> in<00:09:07.480> data<00:09:07.780> gathering<00:09:08.110> because<00:09:08.620> all 00:09:08.940 --> 00:09:08.950 align:start position:0% delay in data gathering because all 00:09:08.950 --> 00:09:11.280 align:start position:0% delay in data gathering because all these<00:09:09.160> actor<00:09:09.580> needs<00:09:09.880> to<00:09:10.120> send<00:09:10.420> data<00:09:10.750> to<00:09:11.140> the 00:09:11.280 --> 00:09:11.290 align:start position:0% these actor needs to send data to the 00:09:11.290 --> 00:09:14.760 align:start position:0% these actor needs to send data to the ministry<00:09:11.800> so<00:09:12.520> they<00:09:13.390> have<00:09:13.570> different<00:09:14.290> days 00:09:14.760 --> 00:09:14.770 align:start position:0% ministry so they have different days 00:09:14.770 --> 00:09:18.030 align:start position:0% ministry so they have different days different<00:09:15.130> laws<00:09:15.640> and<00:09:16.320> the<00:09:17.320> ministry<00:09:17.710> can<00:09:17.890> do 00:09:18.030 --> 00:09:18.040 align:start position:0% different laws and the ministry can do 00:09:18.040 --> 00:09:20.010 align:start position:0% different laws and the ministry can do they<00:09:18.160> can<00:09:18.370> really<00:09:18.760> do<00:09:19.000> the<00:09:19.120> math<00:09:19.270> because 00:09:20.010 --> 00:09:20.020 align:start position:0% they can really do the math because 00:09:20.020 --> 00:09:22.260 align:start position:0% they can really do the math because different<00:09:20.440> actors<00:09:21.160> can<00:09:21.400> declare<00:09:21.760> different 00:09:22.260 --> 00:09:22.270 align:start position:0% different actors can declare different 00:09:22.270 --> 00:09:24.660 align:start position:0% different actors can declare different numbers<00:09:22.660> and<00:09:23.110> it's<00:09:23.650> not<00:09:23.770> easy<00:09:23.980> to<00:09:24.220> understand 00:09:24.660 --> 00:09:24.670 align:start position:0% numbers and it's not easy to understand 00:09:24.670 --> 00:09:29.100 align:start position:0% numbers and it's not easy to understand who<00:09:24.880> is<00:09:25.090> saying<00:09:25.420> the<00:09:25.780> true<00:09:26.230> I<00:09:26.410> would<00:09:26.710> say<00:09:28.110> he's 00:09:29.100 --> 00:09:29.110 align:start position:0% who is saying the true I would say he's 00:09:29.110 --> 00:09:32.490 align:start position:0% who is saying the true I would say he's wrong<00:09:29.380> so<00:09:30.120> there<00:09:31.120> are<00:09:31.240> high<00:09:31.570> costs<00:09:31.990> for<00:09:32.050> former 00:09:32.490 --> 00:09:32.500 align:start position:0% wrong so there are high costs for former 00:09:32.500 --> 00:09:34.560 align:start position:0% wrong so there are high costs for former controls<00:09:33.030> because<00:09:34.030> it's<00:09:34.180> a<00:09:34.300> fully 00:09:34.560 --> 00:09:34.570 align:start position:0% controls because it's a fully 00:09:34.570 --> 00:09:36.120 align:start position:0% controls because it's a fully centralized<00:09:35.020> information<00:09:35.260> that<00:09:35.680> is<00:09:35.860> required 00:09:36.120 --> 00:09:36.130 align:start position:0% centralized information that is required 00:09:36.130 --> 00:09:40.380 align:start position:0% centralized information that is required to<00:09:36.400> go<00:09:36.610> to<00:09:36.640> the<00:09:37.830> ministry<00:09:38.830> and<00:09:39.180> there<00:09:40.180> is<00:09:40.270> no 00:09:40.380 --> 00:09:40.390 align:start position:0% to go to the ministry and there is no 00:09:40.390 --> 00:09:42.510 align:start position:0% to go to the ministry and there is no easy<00:09:40.540> access<00:09:40.930> for<00:09:41.170> the<00:09:41.320> consumer<00:09:41.800> to<00:09:41.980> all 00:09:42.510 --> 00:09:42.520 align:start position:0% easy access for the consumer to all 00:09:42.520 --> 00:09:46.490 align:start position:0% easy access for the consumer to all these<00:09:42.820> data<00:09:43.150> so<00:09:43.720> the<00:09:43.840> data<00:09:43.870> is<00:09:44.620> there<00:09:44.980> but<00:09:45.340> is 00:09:46.490 --> 00:09:46.500 align:start position:0% these data so the data is there but is 00:09:46.500 --> 00:09:49.320 align:start position:0% these data so the data is there but is available<00:09:47.500> only<00:09:47.860> for<00:09:48.250> the<00:09:48.310> ministry<00:09:49.150> known 00:09:49.320 --> 00:09:49.330 align:start position:0% available only for the ministry known 00:09:49.330 --> 00:09:55.440 align:start position:0% available only for the ministry known for<00:09:49.600> us<00:09:50.250> so<00:09:51.250> the<00:09:51.880> project<00:09:52.270> is<00:09:52.920> this<00:09:53.920> we<00:09:54.450> set 00:09:55.440 --> 00:09:55.450 align:start position:0% for us so the project is this we set 00:09:55.450 --> 00:09:58.260 align:start position:0% for us so the project is this we set three<00:09:55.660> goals<00:09:55.900> reduce<00:09:56.410> reduce<00:09:57.400> grow<00:09:58.120> up<00:09:58.240> chat 00:09:58.260 --> 00:09:58.270 align:start position:0% three goals reduce reduce grow up chat 00:09:58.270 --> 00:10:00.660 align:start position:0% three goals reduce reduce grow up chat board<00:09:58.810> cut<00:09:58.930> the<00:09:59.050> burdens<00:09:59.470> for<00:10:00.310> actors 00:10:00.660 --> 00:10:00.670 align:start position:0% board cut the burdens for actors 00:10:00.670 --> 00:10:03.500 align:start position:0% board cut the burdens for actors involved<00:10:00.940> in<00:10:01.150> production<00:10:01.630> chain<00:10:02.490> simplify 00:10:03.500 --> 00:10:03.510 align:start position:0% involved in production chain simplify 00:10:03.510 --> 00:10:05.640 align:start position:0% involved in production chain simplify mandatory<00:10:04.510> declaration<00:10:05.260> management 00:10:05.640 --> 00:10:05.650 align:start position:0% mandatory declaration management 00:10:05.650 --> 00:10:07.320 align:start position:0% mandatory declaration management automating<00:10:06.460> the<00:10:06.580> collection<00:10:07.060> of<00:10:07.180> information 00:10:07.320 --> 00:10:07.330 align:start position:0% automating the collection of information 00:10:07.330 --> 00:10:09.960 align:start position:0% automating the collection of information and<00:10:08.170> removing<00:10:08.590> duplicate<00:10:09.010> stale<00:10:09.280> dialogue 00:10:09.960 --> 00:10:09.970 align:start position:0% and removing duplicate stale dialogue 00:10:09.970 --> 00:10:12.840 align:start position:0% and removing duplicate stale dialogue create<00:10:10.900> a<00:10:10.960> certification<00:10:11.440> system<00:10:12.100> based<00:10:12.520> on 00:10:12.840 --> 00:10:12.850 align:start position:0% create a certification system based on 00:10:12.850 --> 00:10:15.480 align:start position:0% create a certification system based on innovative<00:10:13.780> technologies<00:10:14.530> to<00:10:15.040> support<00:10:15.190> the 00:10:15.480 --> 00:10:15.490 align:start position:0% innovative technologies to support the 00:10:15.490 --> 00:10:17.520 align:start position:0% innovative technologies to support the wine<00:10:15.640> supply<00:10:15.970> chain<00:10:16.180> this<00:10:16.780> is<00:10:16.900> important<00:10:17.320> it 00:10:17.520 --> 00:10:17.530 align:start position:0% wine supply chain this is important it 00:10:17.530 --> 00:10:19.830 align:start position:0% wine supply chain this is important it should<00:10:17.590> not<00:10:18.190> be<00:10:18.430> it<00:10:19.210> should<00:10:19.270> be<00:10:19.480> coordinated 00:10:19.830 --> 00:10:19.840 align:start position:0% should not be it should be coordinated 00:10:19.840 --> 00:10:21.720 align:start position:0% should not be it should be coordinated and<00:10:20.260> supervised<00:10:20.680> by<00:10:20.710> the<00:10:20.980> Ministry<00:10:21.130> but 00:10:21.720 --> 00:10:21.730 align:start position:0% and supervised by the Ministry but 00:10:21.730 --> 00:10:27.600 align:start position:0% and supervised by the Ministry but freely<00:10:22.620> freely<00:10:23.620> usable<00:10:24.550> by<00:10:25.150> the<00:10:25.840> market<00:10:26.610> SME 00:10:27.600 --> 00:10:27.610 align:start position:0% freely freely usable by the market SME 00:10:27.610 --> 00:10:30.720 align:start position:0% freely freely usable by the market SME retailer<00:10:28.210> setup<00:10:28.660> for<00:10:29.320> building<00:10:29.650> the<00:10:29.950> veil<00:10:30.160> of 00:10:30.720 --> 00:10:30.730 align:start position:0% retailer setup for building the veil of 00:10:30.730 --> 00:10:33.240 align:start position:0% retailer setup for building the veil of value-added<00:10:31.330> services<00:10:31.690> and<00:10:32.130> enable<00:10:33.130> more 00:10:33.240 --> 00:10:33.250 align:start position:0% value-added services and enable more 00:10:33.250 --> 00:10:35.300 align:start position:0% value-added services and enable more effective<00:10:33.670> control<00:10:34.000> management<00:10:34.360> by 00:10:35.300 --> 00:10:35.310 align:start position:0% effective control management by 00:10:35.310 --> 00:10:38.940 align:start position:0% effective control management by organizations<00:10:36.310> so<00:10:36.750> how<00:10:37.750> we<00:10:37.810> do<00:10:38.080> it<00:10:38.230> with<00:10:38.440> an 00:10:38.940 --> 00:10:38.950 align:start position:0% organizations so how we do it with an 00:10:38.950 --> 00:10:45.540 align:start position:0% organizations so how we do it with an English<00:10:39.600> 3.4<00:10:42.270> 4.0<00:10:43.920> supply<00:10:44.920> chain<00:10:45.100> platform 00:10:45.540 --> 00:10:45.550 align:start position:0% English 3.4 4.0 supply chain platform 00:10:45.550 --> 00:10:47.100 align:start position:0% English 3.4 4.0 supply chain platform for<00:10:45.760> through<00:10:45.910> Sabido<00:10:46.180> grapes<00:10:46.510> transport 00:10:47.100 --> 00:10:47.110 align:start position:0% for through Sabido grapes transport 00:10:47.110 --> 00:10:49.410 align:start position:0% for through Sabido grapes transport processing<00:10:47.530> and<00:10:47.680> bottling<00:10:48.040> well<00:10:48.670> the<00:10:49.030> benefit 00:10:49.410 --> 00:10:49.420 align:start position:0% processing and bottling well the benefit 00:10:49.420 --> 00:10:50.940 align:start position:0% processing and bottling well the benefit admits<00:10:49.930> that<00:10:49.960> even<00:10:50.110> for<00:10:50.380> my<00:10:50.500> suspect 00:10:50.940 --> 00:10:50.950 align:start position:0% admits that even for my suspect 00:10:50.950 --> 00:10:53.329 align:start position:0% admits that even for my suspect simplification<00:10:52.050> facility 00:10:53.329 --> 00:10:53.339 align:start position:0% simplification facility 00:10:53.339 --> 00:10:56.910 align:start position:0% simplification facility certified<00:10:54.339> and<00:10:54.670> accessible<00:10:55.500> to<00:10:56.500> place<00:10:56.680> and 00:10:56.910 --> 00:10:56.920 align:start position:0% certified and accessible to place and 00:10:56.920 --> 00:10:58.890 align:start position:0% certified and accessible to place and consumer 00:10:58.890 --> 00:10:58.900 align:start position:0% consumer 00:10:58.900 --> 00:11:01.760 align:start position:0% consumer easy<00:10:59.770> sharing<00:11:00.190> of<00:11:00.339> guarantee<00:11:00.700> data<00:11:00.970> for<00:11:01.330> all 00:11:01.760 --> 00:11:01.770 align:start position:0% easy sharing of guarantee data for all 00:11:01.770 --> 00:11:04.890 align:start position:0% easy sharing of guarantee data for all controllers<00:11:02.770> of<00:11:03.070> supply<00:11:03.370> chain<00:11:03.640> and<00:11:03.880> we<00:11:04.810> have 00:11:04.890 --> 00:11:04.900 align:start position:0% controllers of supply chain and we have 00:11:04.900 --> 00:11:06.070 align:start position:0% controllers of supply chain and we have real<00:11:05.110> real<00:11:05.680> time<00:11:05.860> at 00:11:06.070 --> 00:11:06.080 align:start position:0% real real time at 00:11:06.080 --> 00:11:09.190 align:start position:0% real real time at to<00:11:06.230> product<00:11:06.760> information<00:11:07.990> decreasing<00:11:08.990> cost 00:11:09.190 --> 00:11:09.200 align:start position:0% to product information decreasing cost 00:11:09.200 --> 00:11:10.990 align:start position:0% to product information decreasing cost for<00:11:09.380> formal<00:11:09.650> documentation<00:11:10.010> checking<00:11:10.490> in<00:11:10.670> the 00:11:10.990 --> 00:11:11.000 align:start position:0% for formal documentation checking in the 00:11:11.000 --> 00:11:14.470 align:start position:0% for formal documentation checking in the check<00:11:11.390> of<00:11:12.380> the<00:11:12.710> authenticity<00:11:12.950> of<00:11:13.700> product 00:11:14.470 --> 00:11:14.480 align:start position:0% check of the authenticity of product 00:11:14.480 --> 00:11:19.930 align:start position:0% check of the authenticity of product also<00:11:14.990> aboard<00:11:16.360> we<00:11:17.360> I<00:11:18.170> think<00:11:19.040> all<00:11:19.160> know<00:11:19.610> it<00:11:19.760> is 00:11:19.930 --> 00:11:19.940 align:start position:0% also aboard we I think all know it is 00:11:19.940 --> 00:11:23.200 align:start position:0% also aboard we I think all know it is but<00:11:20.420> we<00:11:21.020> have<00:11:21.130> bandages<00:11:22.130> of<00:11:22.160> lesson<00:11:23.090> right 00:11:23.200 --> 00:11:23.210 align:start position:0% but we have bandages of lesson right 00:11:23.210 --> 00:11:24.850 align:start position:0% but we have bandages of lesson right platform<00:11:23.420> there<00:11:24.080> are<00:11:24.170> no<00:11:24.350> single<00:11:24.530> point<00:11:24.800> of 00:11:24.850 --> 00:11:24.860 align:start position:0% platform there are no single point of 00:11:24.860 --> 00:11:27.460 align:start position:0% platform there are no single point of failure<00:11:25.040> we<00:11:25.640> have<00:11:25.670> cost<00:11:26.090> fairness<00:11:26.510> one<00:11:27.020> of<00:11:27.230> my 00:11:27.460 --> 00:11:27.470 align:start position:0% failure we have cost fairness one of my 00:11:27.470 --> 00:11:30.190 align:start position:0% failure we have cost fairness one of my favorite<00:11:28.220> because<00:11:28.790> reduce<00:11:29.390> cost<00:11:29.660> respect 00:11:30.190 --> 00:11:30.200 align:start position:0% favorite because reduce cost respect 00:11:30.200 --> 00:11:33.070 align:start position:0% favorite because reduce cost respect existing<00:11:30.710> solution<00:11:31.040> and<00:11:31.250> it<00:11:32.240> is<00:11:32.390> a<00:11:32.420> fair<00:11:32.780> this 00:11:33.070 --> 00:11:33.080 align:start position:0% existing solution and it is a fair this 00:11:33.080 --> 00:11:37.090 align:start position:0% existing solution and it is a fair this will<00:11:33.260> cost<00:11:33.560> among<00:11:33.770> all<00:11:33.950> players<00:11:34.420> it's<00:11:35.420> safe<00:11:36.100> we 00:11:37.090 --> 00:11:37.100 align:start position:0% will cost among all players it's safe we 00:11:37.100 --> 00:11:39.910 align:start position:0% will cost among all players it's safe we can<00:11:37.340> run<00:11:37.610> smart<00:11:38.000> contact<00:11:38.420> and<00:11:38.720> we<00:11:39.440> have<00:11:39.560> that 00:11:39.910 --> 00:11:39.920 align:start position:0% can run smart contact and we have that 00:11:39.920 --> 00:11:44.380 align:start position:0% can run smart contact and we have that protection<00:11:40.310> that<00:11:40.760> are<00:11:41.600> immutable<00:11:42.460> almost<00:11:43.460> and 00:11:44.380 --> 00:11:44.390 align:start position:0% protection that are immutable almost and 00:11:44.390 --> 00:11:49.150 align:start position:0% protection that are immutable almost and can<00:11:44.810> be<00:11:45.020> encrypted<00:11:45.700> what<00:11:46.700> it's<00:11:47.030> different<00:11:48.160> the 00:11:49.150 --> 00:11:49.160 align:start position:0% can be encrypted what it's different the 00:11:49.160 --> 00:11:51.090 align:start position:0% can be encrypted what it's different the improvement<00:11:49.550> respect<00:11:50.150> drive<00:11:50.330> of<00:11:50.510> solutions 00:11:51.090 --> 00:11:51.100 align:start position:0% improvement respect drive of solutions 00:11:51.100 --> 00:11:53.680 align:start position:0% improvement respect drive of solutions based<00:11:52.100> on<00:11:52.160> the<00:11:52.250> blockchain<00:11:52.490> already<00:11:53.300> existing 00:11:53.680 --> 00:11:53.690 align:start position:0% based on the blockchain already existing 00:11:53.690 --> 00:11:58.360 align:start position:0% based on the blockchain already existing so<00:11:54.440> we<00:11:55.420> the<00:11:56.420> platform<00:11:56.780> born<00:11:57.440> and<00:11:57.680> dedicated<00:11:58.250> to 00:11:58.360 --> 00:11:58.370 align:start position:0% so we the platform born and dedicated to 00:11:58.370 --> 00:12:00.100 align:start position:0% so we the platform born and dedicated to incentivize<00:11:59.150> collaboration<00:11:59.690> effort<00:11:59.960> so 00:12:00.100 --> 00:12:00.110 align:start position:0% incentivize collaboration effort so 00:12:00.110 --> 00:12:02.770 align:start position:0% incentivize collaboration effort so included<00:12:00.560> encouraging<00:12:01.520> data<00:12:02.030> usage<00:12:02.600> and 00:12:02.770 --> 00:12:02.780 align:start position:0% included encouraging data usage and 00:12:02.780 --> 00:12:05.620 align:start position:0% included encouraging data usage and building<00:12:03.230> new<00:12:03.380> application<00:12:04.630> rehabilitated 00:12:05.620 --> 00:12:05.630 align:start position:0% building new application rehabilitated 00:12:05.630 --> 00:12:08.110 align:start position:0% building new application rehabilitated data<00:12:05.870> data<00:12:06.350> are<00:12:06.560> also<00:12:06.890> certified<00:12:07.550> by<00:12:07.700> public 00:12:08.110 --> 00:12:08.120 align:start position:0% data data are also certified by public 00:12:08.120 --> 00:12:10.570 align:start position:0% data data are also certified by public administration<00:12:08.750> systems<00:12:09.230> not<00:12:10.040> just<00:12:10.370> for 00:12:10.570 --> 00:12:10.580 align:start position:0% administration systems not just for 00:12:10.580 --> 00:12:14.140 align:start position:0% administration systems not just for private<00:12:11.120> individuals<00:12:11.560> it<00:12:12.560> is<00:12:12.800> legal<00:12:13.640> valid 00:12:14.140 --> 00:12:14.150 align:start position:0% private individuals it is legal valid 00:12:14.150 --> 00:12:18.340 align:start position:0% private individuals it is legal valid and<00:12:14.590> there<00:12:15.590> is<00:12:15.710> legally<00:12:16.540> very<00:12:17.540> legal<00:12:18.170> validity 00:12:18.340 --> 00:12:18.350 align:start position:0% and there is legally very legal validity 00:12:18.350 --> 00:12:21.240 align:start position:0% and there is legally very legal validity and<00:12:18.770> simplification<00:12:19.370> involved<00:12:20.210> because<00:12:20.780> we 00:12:21.240 --> 00:12:21.250 align:start position:0% and simplification involved because we 00:12:21.250 --> 00:12:24.210 align:start position:0% and simplification involved because we integrated<00:12:22.250> with<00:12:22.700> the<00:12:22.850> system<00:12:22.880> that<00:12:23.720> already 00:12:24.210 --> 00:12:24.220 align:start position:0% integrated with the system that already 00:12:24.220 --> 00:12:29.830 align:start position:0% integrated with the system that already used<00:12:25.220> by<00:12:26.120> the<00:12:26.180> Ministry<00:12:27.460> and<00:12:28.460> are<00:12:29.090> used<00:12:29.360> to 00:12:29.830 --> 00:12:29.840 align:start position:0% used by the Ministry and are used to 00:12:29.840 --> 00:12:32.770 align:start position:0% used by the Ministry and are used to fulfill<00:12:30.380> various<00:12:31.030> bureaucratic<00:12:32.030> burdens<00:12:32.600> so 00:12:32.770 --> 00:12:32.780 align:start position:0% fulfill various bureaucratic burdens so 00:12:32.780 --> 00:12:37.780 align:start position:0% fulfill various bureaucratic burdens so the<00:12:34.330> company<00:12:35.330> does<00:12:36.260> not<00:12:36.500> any<00:12:36.920> anything<00:12:37.550> at<00:12:37.670> all 00:12:37.780 --> 00:12:37.790 align:start position:0% the company does not any anything at all 00:12:37.790 --> 00:12:41.890 align:start position:0% the company does not any anything at all and<00:12:38.030> you<00:12:38.960> can<00:12:39.200> track<00:12:39.790> the<00:12:40.790> dissipation<00:12:41.750> and 00:12:41.890 --> 00:12:41.900 align:start position:0% and you can track the dissipation and 00:12:41.900 --> 00:12:45.070 align:start position:0% and you can track the dissipation and just<00:12:42.770> now<00:12:42.910> actors<00:12:43.910> would<00:12:44.120> certify<00:12:44.480> the<00:12:44.630> entity 00:12:45.070 --> 00:12:45.080 align:start position:0% just now actors would certify the entity 00:12:45.080 --> 00:12:48.250 align:start position:0% just now actors would certify the entity so<00:12:45.710> we<00:12:46.400> can<00:12:46.580> integrate<00:12:46.790> with<00:12:47.000> the<00:12:47.480> specific 00:12:48.250 --> 00:12:48.260 align:start position:0% so we can integrate with the specific 00:12:48.260 --> 00:12:49.930 align:start position:0% so we can integrate with the specific existing<00:12:48.650> systems<00:12:49.070> for<00:12:49.580> an<00:12:49.670> entire 00:12:49.930 --> 00:12:49.940 align:start position:0% existing systems for an entire 00:12:49.940 --> 00:12:53.020 align:start position:0% existing systems for an entire application<00:12:50.090> for<00:12:50.570> example<00:12:50.750> the<00:12:51.080> IT<00:12:51.910> system<00:12:52.910> of 00:12:53.020 --> 00:12:53.030 align:start position:0% application for example the IT system of 00:12:53.030 --> 00:12:56.020 align:start position:0% application for example the IT system of the<00:12:53.150> ministry<00:12:53.570> or<00:12:53.780> the<00:12:54.040> SPID<00:12:55.040> that<00:12:55.460> is<00:12:55.580> an 00:12:56.020 --> 00:12:56.030 align:start position:0% the ministry or the SPID that is an 00:12:56.030 --> 00:12:56.540 align:start position:0% the ministry or the SPID that is an inertia 00:12:56.540 --> 00:12:56.550 align:start position:0% inertia 00:12:56.550 --> 00:13:00.800 align:start position:0% inertia National<00:12:57.360> Italian<00:12:58.080> unification<00:12:58.410> system<00:12:59.810> it 00:13:00.800 --> 00:13:00.810 align:start position:0% National Italian unification system it 00:13:00.810 --> 00:13:03.650 align:start position:0% National Italian unification system it is<00:13:01.019> a<00:13:01.050> dissolution<00:13:01.740> it<00:13:02.130> is<00:13:02.279> provider<00:13:02.700> ET<00:13:03.240> item 00:13:03.650 --> 00:13:03.660 align:start position:0% is a dissolution it is provider ET item 00:13:03.660 --> 00:13:05.389 align:start position:0% is a dissolution it is provider ET item provides<00:13:03.930> a<00:13:03.990> realistic<00:13:04.290> so<00:13:04.769> every 00:13:05.389 --> 00:13:05.399 align:start position:0% provides a realistic so every 00:13:05.399 --> 00:13:06.980 align:start position:0% provides a realistic so every stakeholder<00:13:05.610> can<00:13:06.000> choose<00:13:06.209> its<00:13:06.480> own<00:13:06.630> IT 00:13:06.980 --> 00:13:06.990 align:start position:0% stakeholder can choose its own IT 00:13:06.990 --> 00:13:09.829 align:start position:0% stakeholder can choose its own IT provider<00:13:07.260> to<00:13:07.620> use<00:13:07.740> the<00:13:08.250> platform<00:13:08.670> it<00:13:09.450> don't 00:13:09.829 --> 00:13:09.839 align:start position:0% provider to use the platform it don't 00:13:09.839 --> 00:13:13.610 align:start position:0% provider to use the platform it don't know<00:13:09.990> they<00:13:10.640> don't<00:13:11.640> need<00:13:11.880> to<00:13:12.120> choose<00:13:12.360> us<00:13:12.570> or<00:13:12.839> the 00:13:13.610 --> 00:13:13.620 align:start position:0% know they don't need to choose us or the 00:13:13.620 --> 00:13:17.420 align:start position:0% know they don't need to choose us or the ministry<00:13:14.010> and<00:13:15.200> save<00:13:16.200> private<00:13:16.920> investment<00:13:17.339> in 00:13:17.420 --> 00:13:17.430 align:start position:0% ministry and save private investment in 00:13:17.430 --> 00:13:20.090 align:start position:0% ministry and save private investment in the<00:13:17.490> ecosystem<00:13:17.910> because<00:13:18.620> it<00:13:19.620> is<00:13:19.800> a<00:13:19.829> real 00:13:20.090 --> 00:13:20.100 align:start position:0% the ecosystem because it is a real 00:13:20.100 --> 00:13:22.069 align:start position:0% the ecosystem because it is a real lasting<00:13:20.339> Livni's<00:13:21.180> on<00:13:21.360> the<00:13:21.720> platform 00:13:22.069 --> 00:13:22.079 align:start position:0% lasting Livni's on the platform 00:13:22.079 --> 00:13:24.410 align:start position:0% lasting Livni's on the platform guaranteed<00:13:22.529> and<00:13:22.769> even<00:13:23.160> if<00:13:23.640> the<00:13:24.000> ministry 00:13:24.410 --> 00:13:24.420 align:start position:0% guaranteed and even if the ministry 00:13:24.420 --> 00:13:26.840 align:start position:0% guaranteed and even if the ministry decide<00:13:25.260> to<00:13:25.500> stop<00:13:25.709> using<00:13:25.860> it<00:13:26.130> the<00:13:26.399> platform<00:13:26.760> is 00:13:26.840 --> 00:13:26.850 align:start position:0% decide to stop using it the platform is 00:13:26.850 --> 00:13:32.050 align:start position:0% decide to stop using it the platform is still<00:13:26.940> there<00:13:28.100> what<00:13:29.100> we<00:13:29.370> created<00:13:29.730> is<00:13:30.200> we<00:13:31.200> choose 00:13:32.050 --> 00:13:32.060 align:start position:0% still there what we created is we choose 00:13:32.060 --> 00:13:35.810 align:start position:0% still there what we created is we choose six<00:13:33.060> players<00:13:33.899> and<00:13:34.170> we<00:13:34.649> created<00:13:34.920> a<00:13:35.310> application 00:13:35.810 --> 00:13:35.820 align:start position:0% six players and we created a application 00:13:35.820 --> 00:13:38.930 align:start position:0% six players and we created a application for<00:13:36.000> everyone<00:13:36.300> so<00:13:36.959> the<00:13:37.829> first<00:13:38.190> is<00:13:38.370> a<00:13:38.399> producer 00:13:38.930 --> 00:13:38.940 align:start position:0% for everyone so the first is a producer 00:13:38.940 --> 00:13:40.880 align:start position:0% for everyone so the first is a producer that<00:13:38.970> send<00:13:39.480> grapes<00:13:39.720> and<00:13:39.990> land<00:13:40.290> information 00:13:40.880 --> 00:13:40.890 align:start position:0% that send grapes and land information 00:13:40.890 --> 00:13:45.190 align:start position:0% that send grapes and land information with<00:13:41.100> a<00:13:41.130> mobile<00:13:41.730> app<00:13:43.220> transporter<00:13:44.220> take<00:13:44.910> that 00:13:45.190 --> 00:13:45.200 align:start position:0% with a mobile app transporter take that 00:13:45.200 --> 00:13:49.100 align:start position:0% with a mobile app transporter take that information<00:13:46.200> and<00:13:47.690> certificate<00:13:48.690> that<00:13:48.839> it 00:13:49.100 --> 00:13:49.110 align:start position:0% information and certificate that it 00:13:49.110 --> 00:13:53.560 align:start position:0% information and certificate that it takes<00:13:49.410> those<00:13:50.029> load<00:13:51.029> and<00:13:51.300> bring<00:13:52.050> to<00:13:52.380> the<00:13:52.529> winery 00:13:53.560 --> 00:13:53.570 align:start position:0% takes those load and bring to the winery 00:13:53.570 --> 00:13:57.410 align:start position:0% takes those load and bring to the winery the<00:13:54.570> winery<00:13:55.279> we<00:13:56.279> operated<00:13:56.790> the<00:13:56.880> system<00:13:57.240> that<00:13:57.390> I 00:13:57.410 --> 00:13:57.420 align:start position:0% the winery we operated the system that I 00:13:57.420 --> 00:14:01.220 align:start position:0% the winery we operated the system that I already<00:13:57.930> use<00:13:58.350> to<00:13:59.660> track<00:14:00.660> this<00:14:00.810> information 00:14:01.220 --> 00:14:01.230 align:start position:0% already use to track this information 00:14:01.230 --> 00:14:04.610 align:start position:0% already use to track this information also<00:14:01.800> on<00:14:01.980> atrium<00:14:02.640> we<00:14:02.970> created<00:14:03.810> dashboard<00:14:04.350> and 00:14:04.610 --> 00:14:04.620 align:start position:0% also on atrium we created dashboard and 00:14:04.620 --> 00:14:09.790 align:start position:0% also on atrium we created dashboard and analytics<00:14:05.130> for<00:14:05.820> the<00:14:06.209> ministry<00:14:07.050> and<00:14:07.290> for<00:14:08.660> to 00:14:09.790 --> 00:14:09.800 align:start position:0% analytics for the ministry and for to 00:14:09.800 --> 00:14:13.100 align:start position:0% analytics for the ministry and for to monitor<00:14:10.800> the<00:14:11.100> the<00:14:11.640> all<00:14:12.149> the<00:14:12.329> transaction<00:14:12.930> and 00:14:13.100 --> 00:14:13.110 align:start position:0% monitor the the all the transaction and 00:14:13.110 --> 00:14:19.490 align:start position:0% monitor the the all the transaction and to<00:14:14.630> apply<00:14:15.630> flood<00:14:16.050> detection<00:14:16.200> and<00:14:17.029> we<00:14:18.500> are 00:14:19.490 --> 00:14:19.500 align:start position:0% to apply flood detection and we are 00:14:19.500 --> 00:14:23.600 align:start position:0% to apply flood detection and we are waiting<00:14:19.709> to<00:14:19.980> create<00:14:20.490> the<00:14:21.920> the<00:14:22.920> step<00:14:23.279> of<00:14:23.520> a 00:14:23.600 --> 00:14:23.610 align:start position:0% waiting to create the the step of a 00:14:23.610 --> 00:14:27.760 align:start position:0% waiting to create the the step of a seaman<00:14:24.060> FC<00:14:24.990> tag<00:14:25.260> eastery<00:14:26.250> to<00:14:26.790> the<00:14:26.910> history<00:14:27.209> and 00:14:27.760 --> 00:14:27.770 align:start position:0% seaman FC tag eastery to the history and 00:14:27.770 --> 00:14:31.730 align:start position:0% seaman FC tag eastery to the history and we<00:14:28.770> created<00:14:29.160> also<00:14:29.310> a<00:14:29.430> web<00:14:29.640> app<00:14:30.020> for<00:14:31.020> a<00:14:31.050> consumer 00:14:31.730 --> 00:14:31.740 align:start position:0% we created also a web app for a consumer 00:14:31.740 --> 00:14:35.990 align:start position:0% we created also a web app for a consumer to<00:14:31.920> verify<00:14:32.760> information<00:14:33.829> how<00:14:34.829> we<00:14:34.860> create<00:14:35.670> this 00:14:35.990 --> 00:14:36.000 align:start position:0% to verify information how we create this 00:14:36.000 --> 00:14:39.230 align:start position:0% to verify information how we create this we<00:14:36.600> use<00:14:37.070> an<00:14:38.070> eye<00:14:38.250> level<00:14:38.430> architecture<00:14:38.670> like 00:14:39.230 --> 00:14:39.240 align:start position:0% we use an eye level architecture like 00:14:39.240 --> 00:14:41.420 align:start position:0% we use an eye level architecture like this<00:14:39.270> which<00:14:39.779> is<00:14:40.079> a<00:14:40.110> platter<00:14:40.770> we<00:14:40.980> are<00:14:41.070> ready<00:14:41.279> on 00:14:41.420 --> 00:14:41.430 align:start position:0% this which is a platter we are ready on 00:14:41.430 --> 00:14:44.269 align:start position:0% this which is a platter we are ready on inside<00:14:42.240> the<00:14:42.480> arm<00:14:42.750> Aviva<00:14:43.110> it's<00:14:43.290> called<00:14:43.620> Otto<00:14:43.800> it 00:14:44.269 --> 00:14:44.279 align:start position:0% inside the arm Aviva it's called Otto it 00:14:44.279 --> 00:14:48.370 align:start position:0% inside the arm Aviva it's called Otto it was<00:14:44.880> born<00:14:45.240> as<00:14:45.660> a<00:14:46.170> night<00:14:46.500> as<00:14:47.430> an<00:14:47.760> IOT<00:14:48.270> platform 00:14:48.370 --> 00:14:48.380 align:start position:0% was born as a night as an IOT platform 00:14:48.380 --> 00:14:51.019 align:start position:0% was born as a night as an IOT platform then<00:14:49.380> evolved<00:14:49.800> as<00:14:50.190> an<00:14:50.399> integration<00:14:50.730> platform 00:14:51.019 --> 00:14:51.029 align:start position:0% then evolved as an integration platform 00:14:51.029 --> 00:14:54.439 align:start position:0% then evolved as an integration platform and<00:14:51.680> now<00:14:52.680> it's<00:14:53.310> also<00:14:53.550> blockchain<00:14:54.029> platform 00:14:54.439 --> 00:14:54.449 align:start position:0% and now it's also blockchain platform 00:14:54.449 --> 00:14:57.860 align:start position:0% and now it's also blockchain platform it's<00:14:55.110> a<00:14:55.199> very<00:14:55.410> high<00:14:55.560> level<00:14:55.860> view<00:14:56.660> overview<00:14:57.660> the 00:14:57.860 --> 00:14:57.870 align:start position:0% it's a very high level view overview the 00:14:57.870 --> 00:15:01.939 align:start position:0% it's a very high level view overview the platform<00:14:58.790> the<00:15:00.019> the<00:15:01.019> main<00:15:01.199> feature<00:15:01.589> of<00:15:01.709> this 00:15:01.939 --> 00:15:01.949 align:start position:0% platform the the main feature of this 00:15:01.949 --> 00:15:05.630 align:start position:0% platform the the main feature of this platform<00:15:02.190> can<00:15:02.430> be<00:15:02.930> mixed<00:15:03.930> so<00:15:04.770> the<00:15:04.949> model<00:15:05.279> can 00:15:05.630 --> 00:15:05.640 align:start position:0% platform can be mixed so the model can 00:15:05.640 --> 00:15:09.920 align:start position:0% platform can be mixed so the model can be<00:15:05.670> mixed<00:15:05.959> as<00:15:06.959> as<00:15:07.470> we<00:15:07.620> wish<00:15:08.029> so 00:15:09.920 --> 00:15:09.930 align:start position:0% be mixed as as we wish so 00:15:09.930 --> 00:15:12.860 align:start position:0% be mixed as as we wish so we<00:15:10.200> create<00:15:10.529> a<00:15:10.730> specific<00:15:11.730> platform<00:15:12.270> for<00:15:12.420> every 00:15:12.860 --> 00:15:12.870 align:start position:0% we create a specific platform for every 00:15:12.870 --> 00:15:19.280 align:start position:0% we create a specific platform for every customer<00:15:13.370> in<00:15:14.420> we<00:15:15.890> work<00:15:16.890> with<00:15:17.070> in<00:15:17.940> this<00:15:18.060> case<00:15:18.300> I 00:15:19.280 --> 00:15:19.290 align:start position:0% customer in we work with in this case I 00:15:19.290 --> 00:15:22.430 align:start position:0% customer in we work with in this case I choose<00:15:20.160> this<00:15:20.279> kind<00:15:20.520> of<00:15:20.700> a<00:15:20.990> summarize<00:15:21.990> a<00:15:22.020> little 00:15:22.430 --> 00:15:22.440 align:start position:0% choose this kind of a summarize a little 00:15:22.440 --> 00:15:25.130 align:start position:0% choose this kind of a summarize a little bit<00:15:22.560> about<00:15:22.760> in<00:15:23.760> this<00:15:23.850> case<00:15:24.000> the<00:15:24.750> supply<00:15:24.990> chain 00:15:25.130 --> 00:15:25.140 align:start position:0% bit about in this case the supply chain 00:15:25.140 --> 00:15:29.180 align:start position:0% bit about in this case the supply chain is<00:15:25.320> this<00:15:25.800> we<00:15:26.040> have<00:15:26.220> on<00:15:26.730> premises<00:15:27.470> solution<00:15:28.470> on 00:15:29.180 --> 00:15:29.190 align:start position:0% is this we have on premises solution on 00:15:29.190 --> 00:15:33.410 align:start position:0% is this we have on premises solution on VMware<00:15:29.700> because<00:15:30.150> ministry<00:15:31.520> product<00:15:32.520> and<00:15:32.940> we 00:15:33.410 --> 00:15:33.420 align:start position:0% VMware because ministry product and we 00:15:33.420 --> 00:15:36.260 align:start position:0% VMware because ministry product and we have<00:15:33.540> a<00:15:33.570> legacy<00:15:34.200> system<00:15:34.710> a<00:15:34.920> you<00:15:35.790> see<00:15:36.000> in<00:15:36.060> grey 00:15:36.260 --> 00:15:36.270 align:start position:0% have a legacy system a you see in grey 00:15:36.270 --> 00:15:39.170 align:start position:0% have a legacy system a you see in grey with<00:15:36.510> Java<00:15:37.100> with<00:15:38.100> Vinnie<00:15:38.370> cultural<00:15:38.790> register 00:15:39.170 --> 00:15:39.180 align:start position:0% with Java with Vinnie cultural register 00:15:39.180 --> 00:15:40.250 align:start position:0% with Java with Vinnie cultural register and<00:15:39.390> other<00:15:39.540> application<00:15:40.080> this<00:15:40.200> application 00:15:40.250 --> 00:15:40.260 align:start position:0% and other application this application 00:15:40.260 --> 00:15:44.360 align:start position:0% and other application this application needs<00:15:40.890> be<00:15:41.150> upgraded<00:15:42.150> to<00:15:42.180> send<00:15:43.310> messages<00:15:44.310> to 00:15:44.360 --> 00:15:44.370 align:start position:0% needs be upgraded to send messages to 00:15:44.370 --> 00:15:46.670 align:start position:0% needs be upgraded to send messages to the<00:15:44.550> data<00:15:44.820> leaks<00:15:45.000> for<00:15:45.510> analytics<00:15:46.050> you<00:15:46.380> see<00:15:46.650> a 00:15:46.670 --> 00:15:46.680 align:start position:0% the data leaks for analytics you see a 00:15:46.680 --> 00:15:49.190 align:start position:0% the data leaks for analytics you see a bunch<00:15:46.980> of<00:15:47.220> a<00:15:47.400> classical<00:15:47.880> a<00:15:48.150> little<00:15:48.870> product 00:15:49.190 --> 00:15:49.200 align:start position:0% bunch of a classical a little product 00:15:49.200 --> 00:15:53.360 align:start position:0% bunch of a classical a little product like<00:15:49.350> elasticsearch<00:15:49.920> Park<00:15:50.990> flora<00:15:51.990> and<00:15:52.500> we 00:15:53.360 --> 00:15:53.370 align:start position:0% like elasticsearch Park flora and we 00:15:53.370 --> 00:15:55.880 align:start position:0% like elasticsearch Park flora and we created<00:15:53.670> the<00:15:53.910> the<00:15:54.720> the<00:15:54.960> front-end<00:15:55.380> we<00:15:55.500> dangled 00:15:55.880 --> 00:15:55.890 align:start position:0% created the the the front-end we dangled 00:15:55.890 --> 00:15:59.110 align:start position:0% created the the the front-end we dangled our<00:15:55.980> engines<00:15:56.430> and<00:15:56.910> the<00:15:57.120> backend<00:15:57.360> API<00:15:57.570> with 00:15:59.110 --> 00:15:59.120 align:start position:0% our engines and the backend API with 00:15:59.120 --> 00:16:04.000 align:start position:0% our engines and the backend API with graphic<00:16:00.120> well<00:16:00.300> and<00:16:00.630> no<00:16:01.050> GS<00:16:01.970> /<00:16:02.970> Sicily<00:16:03.330> is 00:16:04.000 --> 00:16:04.010 align:start position:0% graphic well and no GS / Sicily is 00:16:04.010 --> 00:16:07.519 align:start position:0% graphic well and no GS / Sicily is for<00:16:05.010> blockchain<00:16:05.670> 16<00:16:06.060> we<00:16:06.180> used<00:16:06.420> to<00:16:06.990> client 00:16:07.519 --> 00:16:07.529 align:start position:0% for blockchain 16 we used to client 00:16:07.529 --> 00:16:11.990 align:start position:0% for blockchain 16 we used to client parity<00:16:08.130> and<00:16:08.310> get<00:16:08.850> and<00:16:09.110> get<00:16:10.110> we<00:16:10.500> put<00:16:11.250> get<00:16:11.490> on<00:16:11.700> the 00:16:11.990 --> 00:16:12.000 align:start position:0% parity and get and get we put get on the 00:16:12.000 --> 00:16:19.040 align:start position:0% parity and get and get we put get on the cloud<00:16:12.210> so<00:16:13.310> all<00:16:17.089> actors<00:16:18.089> and<00:16:18.360> third<00:16:18.690> parties 00:16:19.040 --> 00:16:19.050 align:start position:0% cloud so all actors and third parties 00:16:19.050 --> 00:16:22.930 align:start position:0% cloud so all actors and third parties can<00:16:19.080> interact<00:16:19.709> with<00:16:19.800> the<00:16:20.640> ministry<00:16:21.350> or<00:16:22.350> via 00:16:22.930 --> 00:16:22.940 align:start position:0% can interact with the ministry or via 00:16:22.940 --> 00:16:27.260 align:start position:0% can interact with the ministry or via classical<00:16:23.940> way<00:16:25.220> legacy<00:16:26.220> system<00:16:26.550> or<00:16:26.730> directly 00:16:27.260 --> 00:16:27.270 align:start position:0% classical way legacy system or directly 00:16:27.270 --> 00:16:33.769 align:start position:0% classical way legacy system or directly through<00:16:27.750> the<00:16:27.839> blockchain<00:16:30.290> so<00:16:31.290> what<00:16:32.720> now<00:16:33.720> the 00:16:33.769 --> 00:16:33.779 align:start position:0% through the blockchain so what now the 00:16:33.779 --> 00:16:36.980 align:start position:0% through the blockchain so what now the the<00:16:34.410> third<00:16:34.740> part<00:16:34.950> is<00:16:35.100> now<00:16:35.360> sent<00:16:36.360> data<00:16:36.510> directly 00:16:36.980 --> 00:16:36.990 align:start position:0% the third part is now sent data directly 00:16:36.990 --> 00:16:39.199 align:start position:0% the third part is now sent data directly to<00:16:37.170> the<00:16:37.290> ministry<00:16:37.650> tomorrow<00:16:38.550> it<00:16:38.790> will<00:16:38.940> send 00:16:39.199 --> 00:16:39.209 align:start position:0% to the ministry tomorrow it will send 00:16:39.209 --> 00:16:47.350 align:start position:0% to the ministry tomorrow it will send only<00:16:39.450> to<00:16:40.110> the<00:16:40.200> blockchain<00:16:44.360> the<00:16:45.360> same<00:16:45.570> thing 00:16:47.350 --> 00:16:47.360 align:start position:0% only to the blockchain the same thing 00:16:47.360 --> 00:16:49.340 align:start position:0% only to the blockchain the same thing let's<00:16:48.360> say<00:16:48.480> something<00:16:48.779> about<00:16:48.900> the<00:16:49.140> smart 00:16:49.340 --> 00:16:49.350 align:start position:0% let's say something about the smart 00:16:49.350 --> 00:16:51.650 align:start position:0% let's say something about the smart contract 00:16:51.650 --> 00:16:51.660 align:start position:0% 00:16:51.660 --> 00:16:54.740 align:start position:0% we<00:16:52.410> created<00:16:52.770> this<00:16:52.950> platform<00:16:53.190> so<00:16:54.089> everyone<00:16:54.510> can 00:16:54.740 --> 00:16:54.750 align:start position:0% we created this platform so everyone can 00:16:54.750 --> 00:17:03.769 align:start position:0% we created this platform so everyone can work<00:16:55.740> with<00:16:56.010> so<00:16:56.700> as<00:16:57.120> my<00:16:57.300> contest<00:16:57.630> as<00:16:59.839> some<00:17:02.779> so 00:17:03.769 --> 00:17:03.779 align:start position:0% work with so as my contest as some so 00:17:03.779 --> 00:17:05.750 align:start position:0% work with so as my contest as some so everyone<00:17:04.140> can<00:17:04.260> use<00:17:04.410> my<00:17:04.530> contract<00:17:04.949> that<00:17:05.160> is<00:17:05.579> not 00:17:05.750 --> 00:17:05.760 align:start position:0% everyone can use my contract that is not 00:17:05.760 --> 00:17:09.520 align:start position:0% everyone can use my contract that is not contract 00:17:09.520 --> 00:17:09.530 align:start position:0% 00:17:09.530 --> 00:17:17.980 align:start position:0% just<00:17:10.430> a<00:17:10.550> moment<00:17:10.850> okay<00:17:13.510> so<00:17:16.689> everyone<00:17:17.689> can<00:17:17.870> use 00:17:17.980 --> 00:17:17.990 align:start position:0% just a moment okay so everyone can use 00:17:17.990 --> 00:17:21.370 align:start position:0% just a moment okay so everyone can use this<00:17:18.110> must<00:17:18.350> contract<00:17:19.240> the<00:17:20.240> question<00:17:20.930> the 00:17:21.370 --> 00:17:21.380 align:start position:0% this must contract the question the 00:17:21.380 --> 00:17:26.530 align:start position:0% this must contract the question the issue<00:17:21.620> is<00:17:23.199> we<00:17:24.199> can<00:17:24.410> create<00:17:24.650> a<00:17:24.709> supply<00:17:25.189> chain<00:17:25.540> we 00:17:26.530 --> 00:17:26.540 align:start position:0% issue is we can create a supply chain we 00:17:26.540 --> 00:17:29.440 align:start position:0% issue is we can create a supply chain we need<00:17:27.350> governance<00:17:27.920> we<00:17:28.370> need<00:17:28.550> the<00:17:28.760> endorsement 00:17:29.440 --> 00:17:29.450 align:start position:0% need governance we need the endorsement 00:17:29.450 --> 00:17:35.470 align:start position:0% need governance we need the endorsement so<00:17:29.930> the<00:17:30.830> ministry<00:17:31.640> endorsed<00:17:32.180> each<00:17:32.570> step<00:17:34.240> if<00:17:35.240> I 00:17:35.470 --> 00:17:35.480 align:start position:0% so the ministry endorsed each step if I 00:17:35.480 --> 00:17:37.990 align:start position:0% so the ministry endorsed each step if I don't<00:17:35.990> want<00:17:36.230> in<00:17:36.530> the<00:17:36.860> means<00:17:37.340> in<00:17:37.520> darkness<00:17:37.820> I 00:17:37.990 --> 00:17:38.000 align:start position:0% don't want in the means in darkness I 00:17:38.000 --> 00:17:42.370 align:start position:0% don't want in the means in darkness I can<00:17:38.240> use<00:17:38.840> this<00:17:39.650> platform<00:17:40.010> in<00:17:40.400> any<00:17:40.550> case<00:17:41.230> so<00:17:42.230> the 00:17:42.370 --> 00:17:42.380 align:start position:0% can use this platform in any case so the 00:17:42.380 --> 00:17:45.010 align:start position:0% can use this platform in any case so the consumer<00:17:42.920> or<00:17:43.100> every<00:17:43.670> player<00:17:43.970> every<00:17:44.150> actor<00:17:44.810> can 00:17:45.010 --> 00:17:45.020 align:start position:0% consumer or every player every actor can 00:17:45.020 --> 00:17:49.030 align:start position:0% consumer or every player every actor can see<00:17:45.850> who<00:17:46.850> endorsed<00:17:47.360> what's<00:17:48.230> that<00:17:48.500> what<00:17:48.740> step 00:17:49.030 --> 00:17:49.040 align:start position:0% see who endorsed what's that what step 00:17:49.040 --> 00:17:56.230 align:start position:0% see who endorsed what's that what step so<00:17:53.200> so<00:17:54.200> we<00:17:54.800> can<00:17:54.920> see<00:17:55.100> we<00:17:55.370> can<00:17:55.550> say<00:17:55.790> that<00:17:55.970> chain 00:17:56.230 --> 00:17:56.240 align:start position:0% so so we can see we can say that chain 00:17:56.240 --> 00:17:59.920 align:start position:0% so so we can see we can say that chain is<00:17:56.360> dynamic<00:17:58.000> and<00:17:59.000> every<00:17:59.300> step<00:17:59.480> can<00:17:59.750> be 00:17:59.920 --> 00:17:59.930 align:start position:0% is dynamic and every step can be 00:17:59.930 --> 00:18:03.100 align:start position:0% is dynamic and every step can be endorsed<00:18:00.320> by<00:18:00.410> everyone<00:18:01.010> for<00:18:01.910> example<00:18:02.270> we<00:18:02.870> can 00:18:03.100 --> 00:18:03.110 align:start position:0% endorsed by everyone for example we can 00:18:03.110 --> 00:18:08.440 align:start position:0% endorsed by everyone for example we can now<00:18:03.850> the<00:18:05.140> identity<00:18:06.140> of<00:18:06.170> the<00:18:06.880> the<00:18:07.880> company<00:18:08.240> is 00:18:08.440 --> 00:18:08.450 align:start position:0% now the identity of the the company is 00:18:08.450 --> 00:18:10.450 align:start position:0% now the identity of the the company is provided<00:18:08.900> by<00:18:09.020> the<00:18:09.080> ministry<00:18:09.680> but<00:18:10.130> tomorrow 00:18:10.450 --> 00:18:10.460 align:start position:0% provided by the ministry but tomorrow 00:18:10.460 --> 00:18:13.230 align:start position:0% provided by the ministry but tomorrow can<00:18:10.670> be<00:18:10.700> for<00:18:11.060> example<00:18:11.480> and<00:18:11.870> I<00:18:12.410> really<00:18:12.830> see 00:18:13.230 --> 00:18:13.240 align:start position:0% can be for example and I really see 00:18:13.240 --> 00:18:16.870 align:start position:0% can be for example and I really see residency<00:18:14.240> credential<00:18:14.920> maybe<00:18:15.920> using<00:18:16.160> the 00:18:16.870 --> 00:18:16.880 align:start position:0% residency credential maybe using the 00:18:16.880 --> 00:18:19.690 align:start position:0% residency credential maybe using the Oracle<00:18:17.450> is<00:18:17.660> proof<00:18:18.050> of<00:18:18.380> identity<00:18:18.830> and<00:18:19.130> allows 00:18:19.690 --> 00:18:19.700 align:start position:0% Oracle is proof of identity and allows 00:18:19.700 --> 00:18:22.570 align:start position:0% Oracle is proof of identity and allows them<00:18:19.940> to<00:18:20.380> endorse<00:18:21.380> every<00:18:21.770> step<00:18:21.980> in<00:18:22.250> any<00:18:22.370> case 00:18:22.570 --> 00:18:22.580 align:start position:0% them to endorse every step in any case 00:18:22.580 --> 00:18:27.280 align:start position:0% them to endorse every step in any case so<00:18:23.240> it's<00:18:24.140> up<00:18:24.290> to<00:18:24.320> every<00:18:25.030> player<00:18:26.030> of<00:18:26.330> the<00:18:26.690> supply 00:18:27.280 --> 00:18:27.290 align:start position:0% so it's up to every player of the supply 00:18:27.290 --> 00:18:32.260 align:start position:0% so it's up to every player of the supply chain<00:18:27.320> to<00:18:27.710> choose<00:18:27.860> what<00:18:29.920> endorsement<00:18:31.270> to 00:18:32.260 --> 00:18:32.270 align:start position:0% chain to choose what endorsement to 00:18:32.270 --> 00:18:38.730 align:start position:0% chain to choose what endorsement to consider<00:18:33.050> valid<00:18:34.030> the<00:18:35.030> ministry<00:18:35.450> said<00:18:36.350> some 00:18:38.730 --> 00:18:38.740 align:start position:0% 00:18:38.740 --> 00:18:41.770 align:start position:0% constraint<00:18:39.740> about<00:18:40.100> for<00:18:40.430> example<00:18:40.490> the<00:18:41.420> the 00:18:41.770 --> 00:18:41.780 align:start position:0% constraint about for example the the 00:18:41.780 --> 00:18:45.870 align:start position:0% constraint about for example the the quantity<00:18:42.230> so<00:18:42.860> if<00:18:43.100> you<00:18:43.250> produce<00:18:43.820> the 00:18:45.870 --> 00:18:45.880 align:start position:0% quantity so if you produce the 00:18:45.880 --> 00:18:49.240 align:start position:0% quantity so if you produce the fix<00:18:46.880> the<00:18:46.970> amount<00:18:47.240> of<00:18:47.480> wine<00:18:47.899> you<00:18:48.200> cannot<00:18:48.679> bottle 00:18:49.240 --> 00:18:49.250 align:start position:0% fix the amount of wine you cannot bottle 00:18:49.250 --> 00:18:53.830 align:start position:0% fix the amount of wine you cannot bottle more<00:18:49.909> than<00:18:50.270> the<00:18:51.140> capacity<00:18:51.559> of<00:18:51.590> the<00:18:52.809> bottle<00:18:53.809> you 00:18:53.830 --> 00:18:53.840 align:start position:0% more than the capacity of the bottle you 00:18:53.840 --> 00:18:58.510 align:start position:0% more than the capacity of the bottle you have<00:18:53.929> so<00:18:54.770> and<00:18:55.520> I<00:18:56.000> can<00:18:56.779> show<00:18:57.049> you<00:18:57.110> just<00:18:57.520> what 00:18:58.510 --> 00:18:58.520 align:start position:0% have so and I can show you just what 00:18:58.520 --> 00:19:01.990 align:start position:0% have so and I can show you just what they<00:18:58.640> think<00:18:58.850> about<00:19:00.460> upgradable<00:19:01.460> con<00:19:01.640> smart 00:19:01.990 --> 00:19:02.000 align:start position:0% they think about upgradable con smart 00:19:02.000 --> 00:19:04.930 align:start position:0% they think about upgradable con smart contract<00:19:02.390> please<00:19:02.809> do<00:19:03.080> not<00:19:03.230> upgrade<00:19:03.760> its<00:19:04.760> mark 00:19:04.930 --> 00:19:04.940 align:start position:0% contract please do not upgrade its mark 00:19:04.940 --> 00:19:07.330 align:start position:0% contract please do not upgrade its mark on<00:19:05.029> work<00:19:05.270> really<00:19:06.110> fast<00:19:06.409> because<00:19:06.799> I<00:19:07.010> don't<00:19:07.190> have 00:19:07.330 --> 00:19:07.340 align:start position:0% on work really fast because I don't have 00:19:07.340 --> 00:19:11.680 align:start position:0% on work really fast because I don't have so<00:19:08.299> I<00:19:08.510> prefer<00:19:08.870> and<00:19:09.649> I<00:19:09.799> suggest<00:19:10.190> though<00:19:11.029> don't 00:19:11.680 --> 00:19:11.690 align:start position:0% so I prefer and I suggest though don't 00:19:11.690 --> 00:19:14.950 align:start position:0% so I prefer and I suggest though don't upgrade<00:19:12.100> as<00:19:13.100> mark<00:19:13.309> honor<00:19:13.460> because<00:19:13.760> these<00:19:14.390> put 00:19:14.950 --> 00:19:14.960 align:start position:0% upgrade as mark honor because these put 00:19:14.960 --> 00:19:17.529 align:start position:0% upgrade as mark honor because these put a<00:19:15.200> government<00:19:15.740> inside<00:19:16.640> the<00:19:16.970> something<00:19:17.390> that 00:19:17.529 --> 00:19:17.539 align:start position:0% a government inside the something that 00:19:17.539 --> 00:19:19.360 align:start position:0% a government inside the something that should<00:19:17.840> not<00:19:17.960> be<00:19:17.990> government 00:19:19.360 --> 00:19:19.370 align:start position:0% should not be government 00:19:19.370 --> 00:19:23.440 align:start position:0% should not be government it's<00:19:19.789> better<00:19:20.029> to<00:19:21.640> send<00:19:22.640> a<00:19:22.760> message<00:19:23.090> to<00:19:23.270> the 00:19:23.440 --> 00:19:23.450 align:start position:0% it's better to send a message to the 00:19:23.450 --> 00:19:25.570 align:start position:0% it's better to send a message to the clients<00:19:23.840> that<00:19:23.870> does<00:19:24.289> not<00:19:24.440> contract<00:19:24.770> for<00:19:25.399> me 00:19:25.570 --> 00:19:25.580 align:start position:0% clients that does not contract for me 00:19:25.580 --> 00:19:27.899 align:start position:0% clients that does not contract for me for<00:19:26.299> the<00:19:26.510> ministry<00:19:26.960> is<00:19:27.140> not<00:19:27.380> running<00:19:27.590> anymore 00:19:27.899 --> 00:19:27.909 align:start position:0% for the ministry is not running anymore 00:19:27.909 --> 00:19:31.330 align:start position:0% for the ministry is not running anymore okay<00:19:28.909> so<00:19:29.299> if<00:19:29.539> I<00:19:29.659> want<00:19:29.840> to<00:19:29.960> use<00:19:30.080> them<00:19:30.320> that<00:19:31.070> my 00:19:31.330 --> 00:19:31.340 align:start position:0% okay so if I want to use them that my 00:19:31.340 --> 00:19:36.669 align:start position:0% okay so if I want to use them that my code<00:19:31.520> I<00:19:31.730> can<00:19:31.760> continue<00:19:32.270> to<00:19:32.419> use<00:19:32.450> that<00:19:34.840> but<00:19:35.840> I 00:19:36.669 --> 00:19:36.679 align:start position:0% code I can continue to use that but I 00:19:36.679 --> 00:19:40.659 align:start position:0% code I can continue to use that but I know<00:19:37.159> that<00:19:37.549> someone<00:19:38.450> know<00:19:39.409> that<00:19:39.440> test<00:19:40.399> my<00:19:40.520> code 00:19:40.659 --> 00:19:40.669 align:start position:0% know that someone know that test my code 00:19:40.669 --> 00:19:42.850 align:start position:0% know that someone know that test my code is<00:19:41.149> not<00:19:41.330> valid<00:19:41.659> anymore<00:19:41.720> for<00:19:42.200> the<00:19:42.409> for<00:19:42.770> the 00:19:42.850 --> 00:19:42.860 align:start position:0% is not valid anymore for the for the 00:19:42.860 --> 00:19:46.299 align:start position:0% is not valid anymore for the for the ministry<00:19:43.250> okay<00:19:43.700> so<00:19:44.299> I<00:19:44.840> finished<00:19:45.590> the<00:19:45.860> time<00:19:46.039> so 00:19:46.299 --> 00:19:46.309 align:start position:0% ministry okay so I finished the time so 00:19:46.309 --> 00:19:49.659 align:start position:0% ministry okay so I finished the time so this<00:19:46.580> is<00:19:46.730> a<00:19:46.760> really<00:19:47.600> fast<00:19:47.890> some<00:19:48.890> screenshot<00:19:49.520> of 00:19:49.659 --> 00:19:49.669 align:start position:0% this is a really fast some screenshot of 00:19:49.669 --> 00:19:53.919 align:start position:0% this is a really fast some screenshot of our<00:19:50.260> console<00:19:51.789> made<00:19:52.789> in<00:19:52.940> angular<00:19:53.330> that<00:19:53.360> shows 00:19:53.919 --> 00:19:53.929 align:start position:0% our console made in angular that shows 00:19:53.929 --> 00:19:57.240 align:start position:0% our console made in angular that shows the<00:19:54.260> production<00:19:55.220> and<00:19:55.580> supply<00:19:56.390> chain<00:19:56.630> steps 00:19:57.240 --> 00:19:57.250 align:start position:0% the production and supply chain steps 00:19:57.250 --> 00:20:00.310 align:start position:0% the production and supply chain steps it's<00:19:58.250> really<00:19:58.580> fast<00:19:58.789> this<00:19:59.120> is<00:19:59.299> some<00:19:59.750> analytics 00:20:00.310 --> 00:20:00.320 align:start position:0% it's really fast this is some analytics 00:20:00.320 --> 00:20:03.820 align:start position:0% it's really fast this is some analytics from<00:20:00.620> Cabana<00:20:01.460> and<00:20:01.820> we<00:20:02.390> have<00:20:02.620> deviation<00:20:03.620> from 00:20:03.820 --> 00:20:03.830 align:start position:0% from Cabana and we have deviation from 00:20:03.830 --> 00:20:06.669 align:start position:0% from Cabana and we have deviation from the<00:20:04.070> historical<00:20:04.640> series<00:20:04.850> for<00:20:05.120> example<00:20:05.679> this 00:20:06.669 --> 00:20:06.679 align:start position:0% the historical series for example this 00:20:06.679 --> 00:20:12.130 align:start position:0% the historical series for example this is<00:20:06.860> the<00:20:08.230> snapshot<00:20:09.230> for<00:20:09.559> from<00:20:10.220> the<00:20:11.140> mobile 00:20:12.130 --> 00:20:12.140 align:start position:0% is the snapshot for from the mobile 00:20:12.140 --> 00:20:15.549 align:start position:0% is the snapshot for from the mobile application<00:20:12.740> for<00:20:13.750> customers<00:20:14.750> so<00:20:15.110> you<00:20:15.260> can 00:20:15.549 --> 00:20:15.559 align:start position:0% application for customers so you can 00:20:15.559 --> 00:20:19.720 align:start position:0% application for customers so you can scan<00:20:16.370> the<00:20:16.549> NFC<00:20:16.940> call<00:20:17.149> and<00:20:17.539> see<00:20:18.010> she<00:20:19.010> code<00:20:19.250> on 00:20:19.720 --> 00:20:19.730 align:start position:0% scan the NFC call and see she code on 00:20:19.730 --> 00:20:23.110 align:start position:0% scan the NFC call and see she code on the<00:20:20.120> bottle<00:20:20.480> and<00:20:20.890> check<00:20:21.890> all<00:20:22.309> the<00:20:22.610> step<00:20:22.880> of 00:20:23.110 --> 00:20:23.120 align:start position:0% the bottle and check all the step of 00:20:23.120 --> 00:20:27.690 align:start position:0% the bottle and check all the step of history<00:20:23.659> and<00:20:24.610> understand<00:20:25.610> where<00:20:25.820> the<00:20:26.360> wine<00:20:27.140> is 00:20:27.690 --> 00:20:27.700 align:start position:0% history and understand where the wine is 00:20:27.700 --> 00:20:33.010 align:start position:0% history and understand where the wine is is<00:20:28.700> made<00:20:28.909> from<00:20:29.299> and<00:20:29.860> so<00:20:30.880> one<00:20:31.880> last<00:20:32.210> thing 00:20:33.010 --> 00:20:33.020 align:start position:0% is made from and so one last thing 00:20:33.020 --> 00:20:35.799 align:start position:0% is made from and so one last thing tomorrow<00:20:33.230> the<00:20:33.620> story<00:20:33.890> is<00:20:34.510> yeah 00:20:35.799 --> 00:20:35.809 align:start position:0% tomorrow the story is yeah 00:20:35.809 --> 00:20:40.060 align:start position:0% tomorrow the story is yeah you<00:20:36.080> may<00:20:36.289> radiate<00:20:37.039> off<00:20:37.460> this<00:20:37.929> somewhere<00:20:39.070> by 00:20:40.060 --> 00:20:40.070 align:start position:0% you may radiate off this somewhere by 00:20:40.070 --> 00:20:44.110 align:start position:0% you may radiate off this somewhere by someone<00:20:40.429> and<00:20:40.690> you<00:20:41.690> can<00:20:41.929> build<00:20:42.230> a<00:20:43.010> tedium<00:20:43.640> and 00:20:44.110 --> 00:20:44.120 align:start position:0% someone and you can build a tedium and 00:20:44.120 --> 00:20:46.870 align:start position:0% someone and you can build a tedium and there's<00:20:45.020> a<00:20:45.080> nice<00:20:45.260> application<00:20:45.520> now<00:20:46.520> in 00:20:46.870 --> 00:20:46.880 align:start position:0% there's a nice application now in 00:20:46.880 --> 00:20:50.560 align:start position:0% there's a nice application now in production<00:20:49.000> don't<00:20:50.000> let<00:20:50.149> them<00:20:50.299> catch<00:20:50.510> you 00:20:50.560 --> 00:20:50.570 align:start position:0% production don't let them catch you 00:20:50.570 --> 00:20:58.420 align:start position:0% production don't let them catch you doing<00:20:50.779> it<00:20:50.990> though<00:20:51.220> thank<00:20:52.220> you 00:20:58.420 --> 00:20:58.430 align:start position:0% 00:20:58.430 --> 00:21:06.009 align:start position:0% [Music]