WEBVTT
Language: en-US

1
00:00:10.220 --> 00:00:12.520
<v John Lester>Hello and welcome to Buildings of
Tomorrow.

2
00:00:12.619 --> 00:00:17.540
<v John Lester>My name is John Lester and in today's
episode we are talking about digitalization in

3
00:00:17.540 --> 00:00:18.069
<v John Lester>fire.

4
00:00:18.540 --> 00:00:23.059
<v John Lester>I'm joined by Peter Nibeker, he is the
head of fire safety products at Siemens

5
00:00:23.059 --> 00:00:24.200
<v John Lester>Smart-Infrastructure.

6
00:00:24.579 --> 00:00:26.440
<v John Lester>Uh, Peter, thank you so much for joining
us.

7
00:00:26.739 --> 00:00:29.079
<v Peter Nebiker>Hi John, uh glad being here today.

8
00:00:29.750 --> 00:00:32.959
<v John Lester>It's great to have you, and what I'm
excited about is talking a little bit about

9
00:00:32.959 --> 00:00:36.599
<v John Lester>digitalization, because in the past we've
talked about fire safety and the

10
00:00:36.599 --> 00:00:41.430
<v John Lester>importance of fire safety, the scope of
fire safety in, in previous episodes, uh,

11
00:00:41.549 --> 00:00:46.639
<v John Lester>and we've also talked with different
guests around smart buildings, and one of those

12
00:00:46.639 --> 00:00:49.880
<v John Lester>core themes, or the two core themes I'd
like to join a little bit together with you

13
00:00:49.880 --> 00:00:53.479
<v John Lester>today because we talk about the importance
of digitalization, we talk about the

14
00:00:53.479 --> 00:00:55.639
<v John Lester>importance of, of connectivity.

15
00:00:56.220 --> 00:00:58.419
<v John Lester>Uh, let's start at the start from your
perspective.

16
00:00:58.500 --> 00:01:01.069
<v John Lester>When we, when we say digitalization, what
does that mean?

17
00:01:01.840 --> 00:01:05.559
<v Peter Nebiker>Well, John, digitalization is, is a big
word.

18
00:01:05.930 --> 00:01:11.730
<v Peter Nebiker>Let me take a step back and reflect the
meaning of digitalization in terms of fire

19
00:01:11.730 --> 00:01:13.680
<v Peter Nebiker>detection from my point of view.

20
00:01:14.459 --> 00:01:21.349
<v Peter Nebiker>So digitalization is all about
connectivity and information, having access

21
00:01:21.349 --> 00:01:26.959
<v Peter Nebiker>to data, integrate and combine some all
kinds of relevant.

22
00:01:27.779 --> 00:01:34.069
<v Peter Nebiker>Business information, buildings
information, system and device information and

23
00:01:34.069 --> 00:01:36.489
<v Peter Nebiker>actually with one purpose at the end.

24
00:01:37.199 --> 00:01:43.889
<v Peter Nebiker>To improve the efficiency and also to
create additional user experience, so to

25
00:01:43.889 --> 00:01:48.589
<v Peter Nebiker>have more safety, more security, and also
more well-being.

26
00:01:49.169 --> 00:01:53.690
<v John Lester>Perfect, so, so it's that connectivity,
it's that ability to collect information to

27
00:01:53.690 --> 00:01:58.209
<v John Lester>get transparency, to ultimately deliver a
better experience, more safety, more

28
00:01:58.209 --> 00:02:00.129
<v John Lester>security, more well-being, as you
mentioned.

29
00:02:00.599 --> 00:02:05.360
<v John Lester>Now, you know, what I, what I'm really
excited about for today's conversation is, is

30
00:02:05.360 --> 00:02:09.600
<v John Lester>your knowledge and experience in the
industry, uh, and it's one of the important

31
00:02:09.600 --> 00:02:13.520
<v John Lester>parts when we talk about digitalization
and we start to try and turn it into the

32
00:02:13.520 --> 00:02:13.880
<v John Lester>real life.

33
00:02:13.919 --> 00:02:18.360
<v John Lester>We have to understand the industry, we
have to know the situations where, where it

34
00:02:18.360 --> 00:02:19.320
<v John Lester>can have a positive effect.

35
00:02:19.429 --> 00:02:23.789
<v John Lester>So I wanted to ask you quickly, if you had
an example in, you know, from, from the,

36
00:02:24.039 --> 00:02:28.000
<v John Lester>your hands-on experience, from the time
that you spend in the industry, if you have

37
00:02:28.000 --> 00:02:33.600
<v John Lester>some, So an example of a situation, a use
case where digitalization can really add

38
00:02:33.600 --> 00:02:34.990
<v John Lester>value and and show benefit.

39
00:02:36.160 --> 00:02:36.839
<v Peter Nebiker>Yes, sure.

40
00:02:37.360 --> 00:02:42.139
<v Peter Nebiker>I mean the introduction I gave you to the
digitalization in terms of fire safety,

41
00:02:42.679 --> 00:02:44.600
<v Peter Nebiker>that sounds quite theoretical.

42
00:02:44.759 --> 00:02:49.559
<v Peter Nebiker>I'd like to share some personal
experiences also with fire detection systems.

43
00:02:50.929 --> 00:02:57.869
<v Peter Nebiker>You know already, I grew up in a family
owned business environment and of course we

44
00:02:57.869 --> 00:03:04.789
<v Peter Nebiker>had a fire detection and at that time,
like most of the systems still today, the

45
00:03:04.789 --> 00:03:06.869
<v Peter Nebiker>system was completely standalone.

46
00:03:07.029 --> 00:03:12.229
<v Peter Nebiker>That means it was just connected to the
fire brigade and an alarm receiving center.

47
00:03:13.740 --> 00:03:19.509
<v Peter Nebiker>Now twice over some time there was a real
fire detector detected and we were really

48
00:03:19.509 --> 00:03:26.070
<v Peter Nebiker>lucky, so the fire brigade was
automatically called and serious damages could

49
00:03:26.070 --> 00:03:27.179
<v Peter Nebiker>definitely be avoided.

50
00:03:28.070 --> 00:03:33.470
<v Peter Nebiker>Now the issue is, since the alarm was
triggered during the night, nobody was able to

51
00:03:33.470 --> 00:03:39.630
<v Peter Nebiker>check from remote in which location the
fire developed and assess the risk until the

52
00:03:39.630 --> 00:03:41.149
<v Peter Nebiker>fire brigade was on site.

53
00:03:41.649 --> 00:03:48.250
<v Peter Nebiker>Wouldn't, wouldn't it have been cool just
to know in the time of the alarm

54
00:03:48.429 --> 00:03:53.509
<v Peter Nebiker>where the alarm was triggered and how the
fire developed.

55
00:03:54.440 --> 00:04:00.839
<v Peter Nebiker>The second experience Unfortunately, and
it was really on rare occasions,

56
00:04:01.369 --> 00:04:07.850
<v Peter Nebiker>the system showed some failure and because
it was installed in a pretty harsh

57
00:04:07.850 --> 00:04:13.850
<v Peter Nebiker>environment and automatically the alarm
receiving center was informed, which then

58
00:04:13.850 --> 00:04:20.049
<v Peter Nebiker>called at that time my parents' home again
and as it is with all these faults, it

59
00:04:20.049 --> 00:04:21.369
<v Peter Nebiker>was in the middle of the night.

60
00:04:22.500 --> 00:04:28.299
<v Peter Nebiker>And now how were my parents supposed to
solve the problem of the alarm system?

61
00:04:28.380 --> 00:04:32.619
<v Peter Nebiker>I mean, they didn't know anything about
the details of the alarm system, and I was

62
00:04:32.619 --> 00:04:38.260
<v Peter Nebiker>always wondering why the system wouldn't
connect to the supplier directly, which

63
00:04:38.260 --> 00:04:43.040
<v Peter Nebiker>could assess the situation from remote and
take the necessary actions.

64
00:04:43.450 --> 00:04:48.970
<v Peter Nebiker>And that's a bit my experience with the
with the fire detection system, and I think

65
00:04:48.970 --> 00:04:53.109
<v Peter Nebiker>today digitalization may really help to
improve these situations.

66
00:04:54.049 --> 00:04:58.690
<v John Lester>Thanks Peter, great examples of a couple
of situations where you know that insight

67
00:04:58.690 --> 00:05:02.369
<v John Lester>and that ability to connect remotely, get
transparency, and even connect to the

68
00:05:02.369 --> 00:05:04.250
<v John Lester>right people could make a benefit.

69
00:05:04.649 --> 00:05:09.109
<v John Lester>And, and this remote connectivity is, is
in many cases driven by cloud connectivity.

70
00:05:09.559 --> 00:05:14.089
<v John Lester>Can you give us an example of, of some of
the main benefits offered by our ability

71
00:05:14.089 --> 00:05:15.170
<v John Lester>to connect via the cloud?

72
00:05:16.480 --> 00:05:22.420
<v Peter Nebiker>Sure, I said, nowadays systems, they may
connect to the cloud and

73
00:05:22.420 --> 00:05:28.600
<v Peter Nebiker>exchange system relevant information and
that continuously with the suppliers,

74
00:05:28.809 --> 00:05:32.380
<v Peter Nebiker>facility managers, and even the building
owners.

75
00:05:33.119 --> 00:05:39.760
<v Peter Nebiker>Now, in case of an alarm, as I said in my
first example, the fire brigade or

76
00:05:39.760 --> 00:05:42.859
<v Peter Nebiker>owner, they may assess the situation.

77
00:05:44.000 --> 00:05:50.799
<v Peter Nebiker>Even before anyone is on site and
therefore they can gain additional time

78
00:05:50.799 --> 00:05:53.089
<v Peter Nebiker>for taking the optimal decisions.

79
00:05:53.559 --> 00:05:59.119
<v Peter Nebiker>Now in the second case, when a system is
unfortunately not functioning properly.

80
00:05:59.739 --> 00:06:06.579
<v Peter Nebiker>The system builder or also the service
provider is automatically informed by cloud

81
00:06:06.579 --> 00:06:13.239
<v Peter Nebiker>connections on the detailed course, and a
fast diagnosis can be possible.

82
00:06:13.420 --> 00:06:18.570
<v Peter Nebiker>Unnecessary actions can be taken
immediately and then without having to disturb the

83
00:06:18.570 --> 00:06:23.160
<v Peter Nebiker>owner, uh, as in our case, in the middle
of the night.

84
00:06:24.130 --> 00:06:31.130
<v Peter Nebiker>And furthermore, this connecting the
system to the cloud and knowing at any time the

85
00:06:31.130 --> 00:06:31.880
<v Peter Nebiker>status.

86
00:06:32.700 --> 00:06:39.500
<v Peter Nebiker>Even before a system failure may occur,
this facilitates an incident management

87
00:06:39.500 --> 00:06:41.700
<v Peter Nebiker>by the service providers.

88
00:06:42.559 --> 00:06:49.480
<v Peter Nebiker>To maximize the performance and change
from today's really prescriptive

89
00:06:49.480 --> 00:06:53.299
<v Peter Nebiker>maintenance schemes to a predictive
maintenance,

90
00:06:53.799 --> 00:07:00.290
<v John Lester>that's a great example and like you
describe, a really interesting way for for this

91
00:07:00.600 --> 00:07:03.119
<v John Lester>process to be driven using cloud
connectivity.

92
00:07:03.589 --> 00:07:06.670
<v John Lester>And, and we talked there about performance
and, and the reaction in a couple of

93
00:07:06.670 --> 00:07:07.570
<v John Lester>different situations.

94
00:07:07.709 --> 00:07:11.839
<v John Lester>How can, how can that cloud connectivity
really help maximize the safety delivery

95
00:07:11.839 --> 00:07:14.959
<v John Lester>like you mentioned at the start, the, the
main goals, or one of the main goals of

96
00:07:14.959 --> 00:07:17.079
<v John Lester>this industry to really maximize that
safety.

97
00:07:17.709 --> 00:07:23.679
<v Peter Nebiker>Now at the end of the day it's all about
maximizing safety and having less

98
00:07:23.679 --> 00:07:26.380
<v Peter Nebiker>disturbance in the building as possible.

99
00:07:26.760 --> 00:07:33.640
<v Peter Nebiker>Now the issue is a bit the
parametricization of a fire detection system is always a

100
00:07:33.640 --> 00:07:35.579
<v Peter Nebiker>difficult trade-off between.

101
00:07:36.190 --> 00:07:42.070
<v Peter Nebiker>A fast response to a real fire and a
robustness to a deceptive phenomenon.

102
00:07:43.420 --> 00:07:49.459
<v Peter Nebiker>A false alarm may interfere with business
operations significantly, as we know now

103
00:07:49.459 --> 00:07:55.480
<v Peter Nebiker>today, detectors with the in-built testing
functionalities, they ensure proper

104
00:07:55.480 --> 00:08:01.140
<v Peter Nebiker>operation as best as possible, connecting
these IoT enabled fire detectors

105
00:08:01.140 --> 00:08:06.299
<v Peter Nebiker>furthermore to the cloud and analyzing the
sensor data continuously.

106
00:08:06.750 --> 00:08:13.019
<v Peter Nebiker>Allows an optimized setting of the
detection properties responsive to the specific

107
00:08:13.019 --> 00:08:13.910
<v Peter Nebiker>application and case.

108
00:08:14.510 --> 00:08:16.130
<v Peter Nebiker>Just make an example.

109
00:08:16.390 --> 00:08:23.209
<v Peter Nebiker>Take an office building and after one
year, the facility manager

110
00:08:23.390 --> 00:08:27.829
<v Peter Nebiker>has a look at all the data which was
collected by the detector.

111
00:08:28.179 --> 00:08:34.099
<v Peter Nebiker>And they see the detective hasn't seen
anything near to a fire alarm that gives a

112
00:08:34.099 --> 00:08:40.780
<v Peter Nebiker>clear indication that the sensitivity of
the detector is too robust and the

113
00:08:40.780 --> 00:08:47.239
<v Peter Nebiker>facility manager, he may approach the end
user or the tenant

114
00:08:47.460 --> 00:08:53.419
<v Peter Nebiker>and discuss with him the possibility to
increase the sensitivity and then also to

115
00:08:53.419 --> 00:08:56.820
<v Peter Nebiker>maximize the safety.

116
00:08:57.390 --> 00:09:00.619
<v Peter Nebiker>Without compromising the normal business
operation,

117
00:09:01.270 --> 00:09:06.820
<v John Lester>right, so that's a really nice additional
use case where we talk about not just the

118
00:09:06.820 --> 00:09:12.359
<v John Lester>response to an event and improving the
ability to protect assets, to protect people,

119
00:09:12.559 --> 00:09:15.840
<v John Lester>protect life, but also minimize the
effects of an event.

120
00:09:16.159 --> 00:09:20.210
<v John Lester>And hopefully turn it into a non-event,
but also really ensuring that that

121
00:09:20.210 --> 00:09:25.270
<v John Lester>protection is, is tailored specifically
for the use case because your example is an

122
00:09:25.270 --> 00:09:25.869
<v John Lester>office building.

123
00:09:26.330 --> 00:09:30.049
<v John Lester>If we look at an office building, every
floor may be used for different things and

124
00:09:30.049 --> 00:09:34.549
<v John Lester>therefore need different requirements to
ensure that safety and have that balance.

125
00:09:35.250 --> 00:09:37.440
<v John Lester>Now, you use the example of an office
there.

126
00:09:37.479 --> 00:09:43.080
<v John Lester>I, I'd like to ask you for another example
um of maybe some more critical

127
00:09:43.080 --> 00:09:47.599
<v John Lester>infrastructure because, Because when we
talk about false alarms and we talk about

128
00:09:47.599 --> 00:09:52.359
<v John Lester>this balance between not disrupting
business but still delivering safety, uh, you

129
00:09:52.359 --> 00:09:57.080
<v John Lester>know, we have some situations in our
infrastructure that are are are really

130
00:09:57.080 --> 00:09:57.630
<v John Lester>critical.

131
00:09:58.030 --> 00:09:59.619
<v John Lester>Do you have another example for us?

132
00:10:00.390 --> 00:10:04.440
<v Peter Nebiker>Uh yes, John, let me take the example of a
hospital.

133
00:10:05.409 --> 00:10:08.239
<v Peter Nebiker>What is the impact if there is a false
alarm?

134
00:10:09.169 --> 00:10:14.630
<v Peter Nebiker>It's clear it might be that essential
health care procedures, they may be

135
00:10:14.630 --> 00:10:16.489
<v Peter Nebiker>interrupted interrupted.

136
00:10:16.849 --> 00:10:19.590
<v Peter Nebiker>Patients may need to be evacuated.

137
00:10:20.340 --> 00:10:24.400
<v Peter Nebiker>And the overall critical business
operation is compromised.

138
00:10:25.349 --> 00:10:31.929
<v Peter Nebiker>Now, in case of a real fire, patients may
not be evacuated fast and easily,

139
00:10:32.390 --> 00:10:37.429
<v Peter Nebiker>and therefore, an early detection of a
dangerous situation, that means a fire in

140
00:10:37.429 --> 00:10:41.130
<v Peter Nebiker>this case is crucial to gain reaction
time.

141
00:10:41.969 --> 00:10:48.890
<v Peter Nebiker>So now the inbuilt test functionalities
and the change from prescriptive to

142
00:10:48.890 --> 00:10:55.210
<v Peter Nebiker>predictive service system service lowers
the necessity to access individual patient

143
00:10:55.210 --> 00:10:56.799
<v Peter Nebiker>rooms for maintenance reasons.

144
00:10:57.500 --> 00:11:04.469
<v Peter Nebiker>So as I, as I said, cloud operations and
automated test features, they

145
00:11:04.469 --> 00:11:10.349
<v Peter Nebiker>really help to increase the safety,
especially in hospitals, and minimize the

146
00:11:10.349 --> 00:11:13.369
<v Peter Nebiker>disturbance by maintenance or system
malfunctions.

147
00:11:13.590 --> 00:11:19.229
<v John Lester>Yeah, that's a really, a really important
example because as you described there,

148
00:11:19.270 --> 00:11:24.469
<v John Lester>this is about as critical as it can get
from a, from the impact on, on, on

149
00:11:24.469 --> 00:11:26.650
<v John Lester>infrastructure and the operation of that
infrastructure.

150
00:11:27.099 --> 00:11:30.760
<v John Lester>If we have the ability through these
different technologies like you mentioned, uh,

151
00:11:30.840 --> 00:11:37.570
<v John Lester>to, to test, to, to understand the, the
health of the system but also avoid those

152
00:11:37.979 --> 00:11:42.000
<v John Lester>non-required disruptions, this is a, this
is a massive impact.

153
00:11:42.580 --> 00:11:46.179
<v John Lester>Now let's talk a little bit about, you
know, we, we've, we've talked about

154
00:11:46.179 --> 00:11:50.059
<v John Lester>technology and every time we have a new
technology, every time there is a change and

155
00:11:50.059 --> 00:11:53.679
<v John Lester>a significant shift within the, within an
industry where we try to start doing

156
00:11:53.679 --> 00:11:57.289
<v John Lester>things, and of course the fire safety,
Industries are not, is not the first one

157
00:11:57.289 --> 00:11:58.130
<v John Lester>that's gone through this.

158
00:11:58.760 --> 00:12:01.440
<v John Lester>But these changes sometimes bring with
them some challenges.

159
00:12:02.320 --> 00:12:06.469
<v John Lester>What are the challenges in this situation
when we start to try and apply a

160
00:12:06.469 --> 00:12:10.719
<v John Lester>digitalization approach and some of these
IoT technologies, cloud technologies, to

161
00:12:10.719 --> 00:12:12.090
<v John Lester>the fire safety industry?

162
00:12:12.479 --> 00:12:16.640
<v Peter Nebiker>Any change, as you just said, John, brings
new challenges.

163
00:12:17.400 --> 00:12:23.559
<v Peter Nebiker>So for me one important issue is the
replacement of the manual work by digital means

164
00:12:23.559 --> 00:12:25.280
<v Peter Nebiker>and technology evolutions.

165
00:12:25.559 --> 00:12:29.320
<v Peter Nebiker>That means automation and also remote
maintenance.

166
00:12:30.119 --> 00:12:36.679
<v Peter Nebiker>That will lead to a shift of the business
mix for system integration, integrators

167
00:12:36.679 --> 00:12:38.960
<v Peter Nebiker>and also facility managers.

168
00:12:39.849 --> 00:12:46.599
<v Peter Nebiker>Also, the change as described previously
in the examples from a prescriptive to a

169
00:12:46.599 --> 00:12:52.929
<v Peter Nebiker>predictive maintenance based on data
analytics that will lead to completely new

170
00:12:52.929 --> 00:12:56.049
<v Peter Nebiker>business models, also to new
opportunities.

171
00:12:56.700 --> 00:13:00.979
<v Peter Nebiker>And these new business models, they
require additional knowledge and skills for

172
00:13:00.979 --> 00:13:03.840
<v Peter Nebiker>technicians and also the engineers.

173
00:13:04.849 --> 00:13:11.010
<v Peter Nebiker>And in addition, this new IoT enables
solutions that gather data and send them into

174
00:13:11.010 --> 00:13:11.510
<v Peter Nebiker>the cloud.

175
00:13:11.650 --> 00:13:18.330
<v Peter Nebiker>They generate a need also for experts that
can process these data to

176
00:13:18.330 --> 00:13:20.289
<v Peter Nebiker>derive valuable actions.

177
00:13:21.320 --> 00:13:27.799
<v Peter Nebiker>And last but not least, people are always
afraid, but I think there is no need to be

178
00:13:27.799 --> 00:13:29.789
<v Peter Nebiker>afraid that there will be less jobs.

179
00:13:30.119 --> 00:13:36.580
<v Peter Nebiker>However, the job profiles, they will
eventually change from today's

180
00:13:36.919 --> 00:13:41.400
<v Peter Nebiker>electromechanical expertise to a
multidisciplinary expertise.

181
00:13:43.539 --> 00:13:44.419
<v John Lester>Understand so.

182
00:13:45.030 --> 00:13:49.599
<v John Lester>So there will be a change and a change
from a technology perspective, but also a

183
00:13:49.599 --> 00:13:53.320
<v John Lester>change then from the industry, the skills
that we need, the expertise that's

184
00:13:53.320 --> 00:13:58.789
<v John Lester>required, but that's an opportunity for us
less than than a risk, and I think we see

185
00:13:58.789 --> 00:14:03.320
<v John Lester>that reflected in in other situations
where we've gone through this digitalization

186
00:14:03.320 --> 00:14:03.739
<v John Lester>process.

187
00:14:04.280 --> 00:14:07.960
<v John Lester>So, so Peter, we've talked a little bit
about technology, we've talked about IoT

188
00:14:07.960 --> 00:14:11.099
<v John Lester>detectors and devices, we've talked about
cloud connectivity.

189
00:14:12.630 --> 00:14:16.070
<v John Lester>Every time we talk about connection, every
time we talk about connectivity, we also

190
00:14:16.070 --> 00:14:19.909
<v John Lester>have to have a little bit of a think about
this cybersecurity aspect, um.

191
00:14:21.190 --> 00:14:25.450
<v John Lester>What about cybersecurity in this case,
and, and how, how does it apply and what,

192
00:14:25.549 --> 00:14:28.349
<v John Lester>what needs to be considered when we're
talking here about fire safety?

193
00:14:29.280 --> 00:14:36.059
<v Peter Nebiker>OK, John, you open up a big box, so it's
clear cybersecurity when it comes to

194
00:14:36.059 --> 00:14:38.580
<v Peter Nebiker>connectivity and the cloud for sure.

195
00:14:39.320 --> 00:14:45.500
<v Peter Nebiker>Uh, plays an essential role whenever we
talk about digitalization.

196
00:14:46.450 --> 00:14:51.950
<v Peter Nebiker>Now the standalone systems which we have
most of the systems are actually standalone

197
00:14:51.950 --> 00:14:57.559
<v Peter Nebiker>systems right now, but eventually they
will be connected to the cloud.

198
00:14:57.780 --> 00:15:02.890
<v Peter Nebiker>So as mentioned, These pose some
additional risks.

199
00:15:03.369 --> 00:15:08.570
<v Peter Nebiker>So with all the nice benefits of the
cloud's connectivity, concerned about the IT

200
00:15:08.570 --> 00:15:13.929
<v Peter Nebiker>security must be taken definitely
seriously, especially when it, when it, when it

201
00:15:13.929 --> 00:15:16.270
<v Peter Nebiker>comes to life safety.

202
00:15:16.890 --> 00:15:23.789
<v Peter Nebiker>Now, as a manufacturer, we have adopted a
Cybersecurity

203
00:15:24.510 --> 00:15:29.150
<v Peter Nebiker>thinking or we call it a think security
philosophy in our product development and

204
00:15:29.150 --> 00:15:35.969
<v Peter Nebiker>the life cycle management process, but
Cybersecurity actually is not an issue

205
00:15:35.969 --> 00:15:41.890
<v Peter Nebiker>of a single device owner, but rather poses
a challenge for all interconnected

206
00:15:41.890 --> 00:15:46.669
<v Peter Nebiker>systems within a new or even an existing
IT infrastructure.

207
00:15:47.599 --> 00:15:54.489
<v Peter Nebiker>Furthermore, cybersecurity has also has
not only a technological aspect but also

208
00:15:54.489 --> 00:15:57.739
<v Peter Nebiker>has a process and people aspect too.

209
00:15:58.400 --> 00:16:04.950
<v Peter Nebiker>Therefore, the cybersecurity must be an
integral part of the whole business

210
00:16:04.950 --> 00:16:05.299
<v Peter Nebiker>operation.

211
00:16:05.799 --> 00:16:11.960
<v Peter Nebiker>And so you understand that this topic
cannot be covered in a few sentences and it

212
00:16:11.960 --> 00:16:15.500
<v Peter Nebiker>might be definitely food for another
podcast.

213
00:16:16.200 --> 00:16:18.489
<v Peter Nebiker>I would be happy to do that.

214
00:16:19.039 --> 00:16:19.799
<v John Lester>That sounds perfect.

215
00:16:19.840 --> 00:16:22.640
<v John Lester>And, and, and I think your comments are
100% right.

216
00:16:23.320 --> 00:16:28.400
<v John Lester>Absolutely essential, uh, absolutely a
core part of, of this, and you mentioned

217
00:16:28.400 --> 00:16:33.159
<v John Lester>there the approach taken from your
organization to, to drive this as part of the

218
00:16:33.159 --> 00:16:35.859
<v John Lester>product development, as part of the
product life cycle management.

219
00:16:36.280 --> 00:16:39.359
<v John Lester>But, but I think it is a good topic for us
for one of the future discussions.

220
00:16:39.440 --> 00:16:42.909
<v John Lester>So let's, uh, Let, let's put that on the
list and we can come back to it.

221
00:16:43.369 --> 00:16:44.229
<v John Lester>Looking for it.

222
00:16:44.530 --> 00:16:46.409
<v John Lester>Peter, thanks so much for the, the
explanation.

223
00:16:46.489 --> 00:16:47.880
<v John Lester>Thanks so much for the insight.

224
00:16:47.929 --> 00:16:51.510
<v John Lester>I wanted to see, um, you know, we've
talked about a lot of things, we've talked

225
00:16:51.510 --> 00:16:55.880
<v John Lester>about technology, we've talked about
different use cases, different uh examples, uh,

226
00:16:55.890 --> 00:17:00.280
<v John Lester>within, within building stock where
digitalization can really add benefits.

227
00:17:00.729 --> 00:17:01.929
<v John Lester>Do you, do you have a summary for us?

228
00:17:02.010 --> 00:17:05.130
<v John Lester>Do you, do you have something that you'd
like to highlight for the audience to, to

229
00:17:05.130 --> 00:17:05.969
<v John Lester>close this episode?

230
00:17:06.959 --> 00:17:11.109
<v Peter Nebiker>Yes, first of all, thanks, thanks also to
you, John, for the nice conversation.

231
00:17:12.040 --> 00:17:17.959
<v Peter Nebiker>Uh, what I wanted to share with the
audience is, uh, as I started with my, as I

232
00:17:17.959 --> 00:17:24.290
<v Peter Nebiker>started at the beginning, Digitalization
is all about connectivity and information,

233
00:17:24.619 --> 00:17:31.479
<v Peter Nebiker>and it really brings a lot of
opportunities, but as with all technology,

234
00:17:32.060 --> 00:17:37.579
<v Peter Nebiker>it is useless without people who have the
knowledge to apply it wisely and

235
00:17:37.579 --> 00:17:38.260
<v Peter Nebiker>effectively.

236
00:17:39.250 --> 00:17:40.150
<v John Lester>That's a great way to finish.

237
00:17:40.969 --> 00:17:45.709
<v John Lester>I think that's perfect, Peter, because as
you say, the technology is just

238
00:17:45.709 --> 00:17:49.689
<v John Lester>technology, data is, is just data, it's
not worth anything unless we can use it to

239
00:17:49.689 --> 00:17:53.329
<v John Lester>derive those insights, those valuable
actions that you mentioned before, and, and we

240
00:17:53.329 --> 00:17:56.810
<v John Lester>have the people to do, to do that with the
skills and the knowledge in the industry,

241
00:17:56.890 --> 00:17:57.959
<v John Lester>so it's a great way to finish.

242
00:17:57.969 --> 00:17:59.770
<v John Lester>And, and thank you so much for joining us.

243
00:17:59.810 --> 00:18:00.689
<v John Lester>It was a real pleasure.

244
00:18:01.050 --> 00:18:04.060
<v John Lester>Uh, and I look forward to, to having some
more conversations at some point in the

245
00:18:04.060 --> 00:18:04.439
<v John Lester>future.

246
00:18:04.780 --> 00:18:05.010
<v John Lester>Thanks,

247
00:18:05.099 --> 00:18:07.119
<v Peter Nebiker>John, the pleasure was also on my side.

248
00:18:07.579 --> 00:18:08.109
<v John Lester>Perfect.

249
00:18:08.359 --> 00:18:11.819
<v John Lester>Uh, and a big thank you also to everyone
out there who is listening to us.

250
00:18:11.939 --> 00:18:16.719
<v John Lester>Please remember to like, subscribe,
comment, share this episode, and always look out

251
00:18:16.719 --> 00:18:20.540
<v John Lester>for the new episodes coming every other
week, and definitely some more conversations

252
00:18:20.540 --> 00:18:25.020
<v John Lester>around fire safety and, and the positive
impact that digitalization can have in

253
00:18:25.020 --> 00:18:28.619
<v John Lester>this, this essential and this important
part of the, of the building industry.

254
00:18:28.699 --> 00:18:30.619
<v John Lester>So thank you all, and we'll see you very
soon.
