WEBVTT
Language: en-US

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

2
00:00:12.420 --> 00:00:16.780
<v John Lester>My name is John Lester, and in today's
episode, we are talking about breaking data

3
00:00:16.780 --> 00:00:21.659
<v John Lester>silos and how we can build a higher and a
better user experience for those out there

4
00:00:21.659 --> 00:00:22.920
<v John Lester>in the building industry.

5
00:00:23.299 --> 00:00:25.649
<v John Lester>I'm really lucky to be joined by Alisa
Ronker.

6
00:00:25.739 --> 00:00:29.940
<v John Lester>She is the global head of SAAS sales for
digital buildings at Siemens

7
00:00:29.940 --> 00:00:34.669
<v John Lester>Smart-Infrastructure, and she's a bit of a
returning expert because we've had a

8
00:00:34.669 --> 00:00:36.180
<v John Lester>recording and a conversation before.

9
00:00:36.259 --> 00:00:38.720
<v John Lester>Alisa, thank you so much for coming back.

10
00:00:40.080 --> 00:00:41.400
<v Alisa>Thank you for having me again.

11
00:00:42.700 --> 00:00:43.909
<v John Lester>Uh, it's, it's always fun.

12
00:00:44.279 --> 00:00:45.860
<v John Lester>It's an absolute pleasure as always.

13
00:00:45.950 --> 00:00:49.669
<v John Lester>And, and as I mentioned, we have had a
couple of conversations in the past, and we

14
00:00:49.669 --> 00:00:52.790
<v John Lester>talked a lot about user experience in the
building.

15
00:00:52.869 --> 00:00:58.110
<v John Lester>We talked a lot about the, the, the
tenants and the, and the building users, what

16
00:00:58.110 --> 00:00:59.349
<v John Lester>they experience when they're in.

17
00:00:59.540 --> 00:00:59.869
<v John Lester>Bass.

18
00:00:59.909 --> 00:01:06.029
<v John Lester>And we also talked a little bit about UX
or user experience, and how important it

19
00:01:06.029 --> 00:01:12.160
<v John Lester>was for us as an industry as we start to,
to get more involved in the daily

20
00:01:12.160 --> 00:01:17.629
<v John Lester>operation of, of a tenant, a facility
manager of a building user, and enable them to

21
00:01:17.629 --> 00:01:19.760
<v John Lester>really help achieve their goals in these
buildings.

22
00:01:20.389 --> 00:01:24.349
<v John Lester>So, so we want to talk today a little bit
more about that user experience and

23
00:01:24.349 --> 00:01:28.839
<v John Lester>creating that higher user experience, and
then the link between The data and the

24
00:01:28.839 --> 00:01:32.650
<v John Lester>data that's sometimes siloed and broken up
in the in the business, but before we get

25
00:01:32.650 --> 00:01:34.660
<v John Lester>to the data, let's talk about user
experience.

26
00:01:35.080 --> 00:01:38.889
<v John Lester>For you, when we talk about user
experience in the building, what do we mean?

27
00:01:40.290 --> 00:01:41.569
<v Alisa>Yeah, so that's a very good question.

28
00:01:41.610 --> 00:01:45.769
<v Alisa>I think in general, usually when we talk
about UX in the building, we talk about the

29
00:01:45.769 --> 00:01:49.290
<v Alisa>tenants or the user of the building, their
user journey, and how do they, you know,

30
00:01:49.690 --> 00:01:53.400
<v Alisa>experience any of the activities that they
do inside the building.

31
00:01:53.449 --> 00:01:56.489
<v Alisa>And this is also what we talked about last
time, you know, that the building really

32
00:01:56.489 --> 00:02:00.169
<v Alisa>needs to contribute towards whatever you
try to achieve inside that building.

33
00:02:00.430 --> 00:02:06.190
<v Alisa>But we sometimes forget to talk about UX
also from just a very simple system point

34
00:02:06.190 --> 00:02:10.259
<v Alisa>of view, you know, what, what kind of
systems are you using as a user in the

35
00:02:10.259 --> 00:02:10.630
<v Alisa>building?

36
00:02:10.699 --> 00:02:12.229
<v Alisa>Are those really catering for you?

37
00:02:12.309 --> 00:02:13.350
<v Alisa>Are they intuitive?

38
00:02:13.429 --> 00:02:15.309
<v Alisa>Is that helping you to perform?

39
00:02:15.440 --> 00:02:20.389
<v Alisa>Better in whatever your task is, and I
think we really when speaking about UX in the

40
00:02:20.389 --> 00:02:24.050
<v Alisa>built environment, we really need to kind
of span across both those individual

41
00:02:24.050 --> 00:02:29.029
<v Alisa>systems and the user experience of those
systems to the user experience of the

42
00:02:29.029 --> 00:02:30.399
<v Alisa>actual whole building.

43
00:02:31.350 --> 00:02:32.160
<v John Lester>Yeah, absolutely.

44
00:02:32.479 --> 00:02:36.759
<v John Lester>And, and that's quite a large scope, and
achieving, you know, creating this higher

45
00:02:36.759 --> 00:02:40.880
<v John Lester>user experience and delivering the
different requirements, the different

46
00:02:40.880 --> 00:02:44.160
<v John Lester>expectations from such a broad group is a
little bit of a challenge.

47
00:02:44.600 --> 00:02:48.669
<v John Lester>Why, why is it so hard and why are we
struggling or have we struggled in the past as

48
00:02:48.669 --> 00:02:50.619
<v John Lester>an industry to really deliver this?

49
00:02:52.199 --> 00:02:56.679
<v Alisa>Well, I think as an industry we've been
looking at first of all buildings as, you

50
00:02:56.679 --> 00:03:01.339
<v Alisa>know, kind of I always call them human
warehouses so that they are just these

51
00:03:01.339 --> 00:03:05.339
<v Alisa>physical structures that are there to, you
know, provide a very basic task, and we

52
00:03:05.339 --> 00:03:10.100
<v Alisa>kind of haven't maybe demanded more when
we think about it from the tenant or user

53
00:03:10.100 --> 00:03:11.589
<v Alisa>of the building experience.

54
00:03:11.740 --> 00:03:15.889
<v Alisa>And then if you think about the different
systems that are used to operate the

55
00:03:15.889 --> 00:03:16.389
<v Alisa>building.

56
00:03:16.770 --> 00:03:21.490
<v Alisa>Those have been designed by engineers for
engineers, and you can imagine how, you

57
00:03:21.490 --> 00:03:26.889
<v Alisa>know, it isn't necessarily meant to be
something that's super intuitive and easy to

58
00:03:26.889 --> 00:03:31.070
<v Alisa>onboard and easy to use and I think, you
know, inherently these two.

59
00:03:31.589 --> 00:03:36.550
<v Alisa>Aspects have been kind of building upon
each other to really, yeah, just lose focus

60
00:03:36.550 --> 00:03:39.839
<v Alisa>on the topic of user experience, and I'm
really glad that that's now shifting and

61
00:03:39.839 --> 00:03:43.919
<v Alisa>changing because we no longer talk only
about the physical building, it's also the

62
00:03:43.919 --> 00:03:48.470
<v Alisa>digital building, um, and, you know, the
expectations are just, um, very different

63
00:03:48.470 --> 00:03:50.360
<v Alisa>from what they may be used to be in the
built environment.

64
00:03:50.440 --> 00:03:52.580
<v Alisa>So I think it's a very welcomed change.

65
00:03:53.820 --> 00:03:58.309
<v John Lester>Yeah, a welcome change, but also one that
highlights a little bit of, you know, we

66
00:03:58.309 --> 00:04:01.690
<v John Lester>have some structural challenges when we
start to talk about this digital building

67
00:04:02.330 --> 00:04:06.990
<v John Lester>and these new expectations because, as you
mentioned, many of the systems within the

68
00:04:06.990 --> 00:04:11.699
<v John Lester>buildings were built by engineers for
engineers, but they were also somehow built.

69
00:04:12.145 --> 00:04:16.195
<v John Lester>Uh, in, in a very focused or, or blinkered
manner.

70
00:04:16.234 --> 00:04:20.635
<v John Lester>They, they focused on one thing, they
solved one problem or 11 collection of

71
00:04:20.635 --> 00:04:25.244
<v John Lester>problems, and they were never really
designed to talk to each other, to share

72
00:04:25.304 --> 00:04:29.734
<v John Lester>information, and, and to be open in, in
any way, shape or form.

73
00:04:30.315 --> 00:04:36.375
<v John Lester>How much does that get in the way of us
really building this, this ultimate UX?

74
00:04:37.899 --> 00:04:42.980
<v Alisa>So it is a massive, massive issue, because
we also have regulatory constraints.

75
00:04:43.049 --> 00:04:47.980
<v Alisa>So some systems need to even be closed,
and, and then we have, let's say, a lot of

76
00:04:47.980 --> 00:04:52.700
<v Alisa>proprietary technology that is kind of
trying to be as close as possible to, for,

77
00:04:52.779 --> 00:04:58.010
<v Alisa>you know, to make, let's say, um, vendor
lock in, as we often talk about it in the,

78
00:04:58.059 --> 00:04:59.299
<v Alisa>in the, in the built environment.

79
00:04:59.630 --> 00:05:05.190
<v Alisa>Um, and then even if we try to be open
and, and we try to, you know, um, have as

80
00:05:05.190 --> 00:05:09.679
<v Alisa>much of this kind of breaking of the silos
and, and, um, cross-pollinating data as I

81
00:05:09.679 --> 00:05:15.140
<v Alisa>call it, um, we land into the, the issues
of no one being very used to doing that,

82
00:05:15.160 --> 00:05:17.429
<v Alisa>um, in, in that environment and in that
context.

83
00:05:17.720 --> 00:05:22.630
<v Alisa>So it, it becomes like, um, A major
challenge to solve, and I think this is probably

84
00:05:22.630 --> 00:05:26.750
<v Alisa>one of the major challenges a lot of the
players in the in the building industry are

85
00:05:26.750 --> 00:05:32.190
<v Alisa>trying to solve, how do we create some
kind of a common data model that we can feed

86
00:05:32.190 --> 00:05:36.869
<v Alisa>then all the different, let's say,
systems, applications from in a way that you can

87
00:05:36.869 --> 00:05:40.335
<v Alisa>also allow a kind of cross-pollination
because I think that is where The

88
00:05:40.335 --> 00:05:46.196
<v Alisa>intelligence will increasingly be not only
from a user experience perspective, but I

89
00:05:46.196 --> 00:05:47.515
<v Alisa>think that will all flow into

90
00:05:47.515 --> 00:05:52.555
<v Alisa>that building experience is if you're
actually able to look at all these different

91
00:05:52.555 --> 00:05:56.835
<v Alisa>touch points of that user of building and
what they try to achieve, and it, you

92
00:05:56.835 --> 00:05:59.915
<v Alisa>know, rarely is linked only to 11 system.

93
00:05:59.996 --> 00:06:02.721
<v Alisa>That would be a very Let's say niche user
experience.

94
00:06:02.911 --> 00:06:05.191
<v Alisa>Usually it overlaps with a lot of
different systems.

95
00:06:05.441 --> 00:06:11.282
<v Alisa>So it's vital that we are able to break
down those data silos, bring that data in a

96
00:06:11.282 --> 00:06:17.002
<v Alisa>unified format that we can then easily
build upon and, and create new, new value

97
00:06:17.002 --> 00:06:21.201
<v Alisa>propositions, new, new outcomes for the
users, whatever those might be.

98
00:06:21.929 --> 00:06:22.690
<v John Lester>Yeah, I understand.

99
00:06:22.890 --> 00:06:28.480
<v John Lester>And, and you talk there about, about
breaking down these silos, so this common data

100
00:06:28.480 --> 00:06:30.940
<v John Lester>environment so we can start to collect
information.

101
00:06:31.640 --> 00:06:36.230
<v John Lester>Is it enough to collect it, or how do we,
how do we enable the, you know, the, the

102
00:06:36.230 --> 00:06:39.880
<v John Lester>tenants in the building, the owners of the
building to actually use this data?

103
00:06:40.079 --> 00:06:44.320
<v John Lester>Because, you know, we, we've had many
conversations on, on this show with different,

104
00:06:44.540 --> 00:06:49.399
<v John Lester>uh, different stakeholders about data and,
and one of the common themes is Data for

105
00:06:49.399 --> 00:06:51.739
<v John Lester>data's sake is not really worth much for
us.

106
00:06:51.920 --> 00:06:52.910
<v John Lester>It, it makes us feel good.

107
00:06:53.010 --> 00:06:57.760
<v John Lester>It proves what's possible, but if we can't
use it for stuff, we can't use it to make

108
00:06:57.760 --> 00:06:57.910
<v John Lester>decisions.

109
00:06:57.959 --> 00:06:59.309
<v John Lester>It doesn't add any value.

110
00:06:59.760 --> 00:07:04.600
<v John Lester>How, how do we support in this use case,
when we start to build this user

111
00:07:04.600 --> 00:07:09.510
<v John Lester>experience, how do we support those people
like tenants, like building users to get

112
00:07:09.510 --> 00:07:14.200
<v John Lester>value from this data, even if they're not
engineers, uh, for engineers' sake?

113
00:07:15.369 --> 00:07:16.130
<v Alisa>Yeah, absolutely.

114
00:07:16.250 --> 00:07:20.799
<v Alisa>So I think a few years ago everyone was
focusing on just how do we gather data, like

115
00:07:20.799 --> 00:07:24.609
<v Alisa>the way, how can we just get as much data
as possible and then eventually figure it

116
00:07:24.609 --> 00:07:28.609
<v Alisa>out that we're sitting on a massive data
dump and no one knows what on earth to do

117
00:07:28.609 --> 00:07:28.970
<v Alisa>with it.

118
00:07:29.209 --> 00:07:34.739
<v Alisa>Um, and then, let alone if you figure out
how to, let's say, make some sense of that

119
00:07:34.739 --> 00:07:38.350
<v Alisa>data, maybe in different systems, you run
into the problem, what if something

120
00:07:38.350 --> 00:07:38.700
<v Alisa>changes?

121
00:07:38.779 --> 00:07:40.980
<v Alisa>How do you then maintain this data as
well?

122
00:07:41.290 --> 00:07:45.339
<v Alisa>And you know, for, for this, this common
data environment is, is absolutely vital

123
00:07:45.339 --> 00:07:50.410
<v Alisa>and you know, we have been working towards
this, let's say, in our own development

124
00:07:50.410 --> 00:07:52.179
<v Alisa>activities and maybe more to come in the.

125
00:07:52.279 --> 00:07:55.239
<v Alisa>Future on that front, uh, but also
through, um, acquisitions.

126
00:07:55.320 --> 00:07:59.839
<v Alisa>So we just acquired Ecoomus as a company,
exactly to help in this use case.

127
00:07:59.920 --> 00:08:03.799
<v Alisa>How can you have a common data
environment, um, and kind of build upon a digital

128
00:08:03.799 --> 00:08:08.660
<v Alisa>twin based on this without having to
always be extremely inefficient in updating,

129
00:08:09.010 --> 00:08:12.320
<v Alisa>um, information in, in, uh, all these
various sources.

130
00:08:12.440 --> 00:08:15.260
<v Alisa>So, you know, it's, it's kind of very.

131
00:08:15.910 --> 00:08:21.470
<v Alisa>Basics that we're talking about, but
something that has been surprisingly neglected

132
00:08:21.470 --> 00:08:25.950
<v Alisa>when everyone was just hyping over
collecting as much data as possible and then

133
00:08:25.950 --> 00:08:29.489
<v Alisa>maybe figuring out something to do with
it, but kind of that middle piece of

134
00:08:29.790 --> 00:08:36.770
<v Alisa>deriving a unified way of interpreting
that data has been a little bit maybe

135
00:08:36.950 --> 00:08:39.510
<v Alisa>forgotten in the, in the midst of that
hype.

136
00:08:40.369 --> 00:08:43.570
<v John Lester>Forgotten and maybe even more difficult
than we ever really expected.

137
00:08:43.650 --> 00:08:47.849
<v John Lester>There's probably, you know, this, this,
this common data environment and like you

138
00:08:47.849 --> 00:08:54.849
<v John Lester>mentioned, companies like Eodomos and
others are really building somehow a

139
00:08:54.849 --> 00:08:59.049
<v John Lester>standardized approach to make this easier,
to make this faster, to make this more

140
00:08:59.049 --> 00:09:02.960
<v John Lester>sustainable, because you talked about
maintenance, of course, taking a snapshot of

141
00:09:02.960 --> 00:09:06.849
<v John Lester>data tomorrow doesn't help us the day
after tomorrow unless we're able to maintain

142
00:09:06.849 --> 00:09:08.099
<v John Lester>and manage that moving forward.

143
00:09:08.210 --> 00:09:11.169
<v John Lester>So, That's a huge step in the right
direction.

144
00:09:11.729 --> 00:09:17.330
<v John Lester>When we talk about that user experience
and, and beyond, you know, often, especially

145
00:09:17.330 --> 00:09:22.090
<v John Lester>when we step into the software space, user
experience, people start to, to, to

146
00:09:22.090 --> 00:09:22.510
<v John Lester>think.

147
00:09:23.489 --> 00:09:27.250
<v John Lester>You know, not just about how things look,
but we also talk about the workflows, and,

148
00:09:27.330 --> 00:09:32.929
<v John Lester>and how people then, um, you know, they,
they use a, a, a, a solution and they get

149
00:09:32.929 --> 00:09:36.460
<v John Lester>to a, you know, get to the answer that
they need, they find out the information that

150
00:09:36.460 --> 00:09:36.869
<v John Lester>they need.

151
00:09:37.700 --> 00:09:41.590
<v John Lester>How is modern technology, how, uh, you
know, you mentioned, uh, you know,

152
00:09:41.789 --> 00:09:46.309
<v John Lester>intelligence before, how are we starting
to move as an industry in this direction to

153
00:09:46.309 --> 00:09:52.669
<v John Lester>make the, the usability, but also the
workflows for these target audiences faster,

154
00:09:52.780 --> 00:09:53.969
<v John Lester>easier, and stronger?

155
00:09:55.369 --> 00:09:59.380
<v Alisa>Yeah, I think definitely we used to maybe
look at exactly how do we gather that data

156
00:09:59.380 --> 00:10:03.260
<v Alisa>and then how could we just get
transparency to the status quo of what's, what's

157
00:10:03.260 --> 00:10:07.340
<v Alisa>happening and whilst that's important and
certainly a prerequisite for any

158
00:10:07.340 --> 00:10:12.169
<v Alisa>additional intelligence that only goes so
far if you actually don't have that action

159
00:10:12.169 --> 00:10:16.530
<v Alisa>actionability on that data, and what can
you then or should you be doing next in

160
00:10:16.530 --> 00:10:18.900
<v Alisa>order to perform your task task better?

161
00:10:19.080 --> 00:10:21.059
<v Alisa>And there exactly we need to link to.

162
00:10:21.140 --> 00:10:24.780
<v Alisa>These different workflows, and there are,
you know, so many different workflows that

163
00:10:24.780 --> 00:10:25.580
<v Alisa>happen in a building.

164
00:10:25.659 --> 00:10:29.299
<v Alisa>Of course we have the facility management
are working their own, own things, but we

165
00:10:29.299 --> 00:10:35.419
<v Alisa>have things like costing and you name it,
you know, there is a lot of different or a

166
00:10:35.419 --> 00:10:39.580
<v Alisa>lot of different stakeholders with very
specific workflows, and I think, you know,

167
00:10:39.659 --> 00:10:43.770
<v Alisa>if we manage really well the whole
deriving the data, making intelligence out of it,

168
00:10:43.820 --> 00:10:46.719
<v Alisa>and then feeding that and
cross-pollinating that data.

169
00:10:47.020 --> 00:10:51.020
<v Alisa>All these different stakeholders are able
to actually perform better in whatever

170
00:10:51.020 --> 00:10:57.059
<v Alisa>they are doing on the daily basis, and
this is really where it becomes increasingly

171
00:10:57.059 --> 00:11:01.739
<v Alisa>important that we get out of those silos
because we create much more efficiency also

172
00:11:01.739 --> 00:11:05.059
<v Alisa>from a, let's say, a resourcing point of
view that you don't have to have like kind

173
00:11:05.059 --> 00:11:10.080
<v Alisa>of one person looking after one system,
but you can actually get efficiency across

174
00:11:10.179 --> 00:11:12.789
<v Alisa>as there are some, let's say maybe joint.

175
00:11:13.130 --> 00:11:18.500
<v Alisa>Uh, initiatives that are catering around
that user experience of the building.

176
00:11:19.219 --> 00:11:22.549
<v Alisa>So, but, but this is really something
that, um, as you mentioned, hasn't

177
00:11:22.549 --> 00:11:26.820
<v Alisa>traditionally been addressed so well in
the, in terms of the systems that are

178
00:11:26.820 --> 00:11:31.799
<v Alisa>deployed in a building, and this is
something we massively want to change.

179
00:11:32.840 --> 00:11:33.469
<v John Lester>Yeah, absolutely.

180
00:11:33.750 --> 00:11:38.739
<v John Lester>And like you mentioned before, the reason
we want to break down the silos is because

181
00:11:38.739 --> 00:11:42.150
<v John Lester>different information, different data from
distant systems helps many different

182
00:11:42.150 --> 00:11:42.500
<v John Lester>people.

183
00:11:42.789 --> 00:11:47.340
<v John Lester>So it's that reuse, that access, and the
application of the access to this data to

184
00:11:47.340 --> 00:11:49.890
<v John Lester>these different workflows is really where
the power comes from.

185
00:11:50.659 --> 00:11:55.659
<v John Lester>Otherwise, we do end up back in the same
cycle where we, we build something from

186
00:11:55.659 --> 00:12:00.059
<v John Lester>scratch to, to address one workflow and
then we build something again from scratch

187
00:12:00.059 --> 00:12:03.260
<v John Lester>to address the next workflow, and we end
up with a huge amount of effort.

188
00:12:03.760 --> 00:12:05.559
<v John Lester>To make any serious impact.

189
00:12:05.719 --> 00:12:10.039
<v John Lester>Uh, and the more and more we want to apply
this kind of technology, the more and

190
00:12:10.039 --> 00:12:14.280
<v John Lester>more we need to have freedom of access,
but also the, that ability to

191
00:12:14.280 --> 00:12:14.840
<v John Lester>cross-pollinate.

192
00:12:14.909 --> 00:12:18.320
<v John Lester>I love that, that, that word or that
phrase that you used of cross-pollinating to

193
00:12:18.320 --> 00:12:22.320
<v John Lester>really pick things up from every different
corner and, and bring them together for

194
00:12:22.320 --> 00:12:26.880
<v John Lester>whatever you would need, you need for this
particular workflow without building a

195
00:12:26.880 --> 00:12:28.440
<v John Lester>whole infrastructure around that.

196
00:12:29.049 --> 00:12:34.090
<v John Lester>Um, so we talked in the last few minutes,
we've talked about breaking the data

197
00:12:34.090 --> 00:12:38.719
<v John Lester>silos, bringing that data into this common
data environment where we have some

198
00:12:38.719 --> 00:12:43.169
<v John Lester>consistency in how we collect, how we
maintain, and also how we access that data

199
00:12:43.640 --> 00:12:47.489
<v John Lester>using intelligence, using smart solutions
to then.

200
00:12:49.150 --> 00:12:53.719
<v John Lester>Grab that data and use it to, depending on
the workflow, use it to find solutions

201
00:12:53.719 --> 00:12:59.059
<v John Lester>and find the steps, and then also ensuring
that we have that breadth of, of scope,

202
00:12:59.780 --> 00:13:04.159
<v John Lester>uh, around, you know, not just the, the
individual stakeholders, the users of the

203
00:13:04.159 --> 00:13:08.640
<v John Lester>building, but also the facility managers,
the owners, the operators, and, and all of

204
00:13:08.640 --> 00:13:10.030
<v John Lester>their, their requirements.

205
00:13:10.400 --> 00:13:14.320
<v John Lester>What's our next step as an industry that
is getting better, like you mentioned,

206
00:13:14.690 --> 00:13:17.880
<v John Lester>common and data environments like
companies like Eodomos are starting to push in

207
00:13:17.880 --> 00:13:18.570
<v John Lester>this direction.

208
00:13:19.049 --> 00:13:22.570
<v John Lester>What's the next step as an industry, or
what's the next step for you and your team

209
00:13:22.570 --> 00:13:26.760
<v John Lester>when you're saying, hey, here's this
problem and we're, we're getting close, uh,

210
00:13:26.929 --> 00:13:27.830
<v John Lester>let's make this happen?

211
00:13:29.200 --> 00:13:33.369
<v Alisa>So I think that the transition is towards
a real platform approach, and I know we've

212
00:13:33.369 --> 00:13:37.929
<v Alisa>talked about platforms in terms of smart
buildings for quite a while, but to

213
00:13:37.929 --> 00:13:42.929
<v Alisa>actually have a platform approach in terms
of data as well, um, I think this is

214
00:13:42.929 --> 00:13:44.090
<v Alisa>really where we need to get to.

215
00:13:44.330 --> 00:13:48.679
<v Alisa>And then not only again gathering the data
and having that unified, um, let's say

216
00:13:48.679 --> 00:13:52.570
<v Alisa>data model, but also how do we have AI
enabled.

217
00:13:52.645 --> 00:13:57.705
<v Alisa>Intelligence in terms of interpreting that
data, making smart analytics based on it,

218
00:13:58.044 --> 00:14:03.525
<v Alisa>looking more at the predictive elements
and all of that kind of is building upon the

219
00:14:03.525 --> 00:14:08.684
<v Alisa>fact that we need to have the silos broken
down and and yeah, move towards a real

220
00:14:08.684 --> 00:14:09.284
<v Alisa>platform approach.

221
00:14:09.405 --> 00:14:14.484
<v Alisa>So this is also what what my team is very
heavily working towards at the moment and

222
00:14:14.484 --> 00:14:16.104
<v Alisa>yeah, there are some interesting things to
come.

223
00:14:17.429 --> 00:14:21.260
<v John Lester>Yeah, I think that that's an exciting
thing because it is an industry, something we

224
00:14:21.260 --> 00:14:22.799
<v John Lester>talk about a lot, um.

225
00:14:24.270 --> 00:14:25.780
<v John Lester>Let's call it many people try.

226
00:14:26.090 --> 00:14:29.789
<v John Lester>Uh, it's not easy, but it's certainly an
area, as you mentioned, that we need to get

227
00:14:29.789 --> 00:14:29.909
<v John Lester>to.

228
00:14:29.950 --> 00:14:31.940
<v John Lester>And it's also something that you don't do
alone, right?

229
00:14:31.989 --> 00:14:35.869
<v John Lester>Like we need, there need to be partners,
there need to be people participating from

230
00:14:35.869 --> 00:14:38.630
<v John Lester>different corners of the market with
different skills and different assets.

231
00:14:38.669 --> 00:14:42.750
<v John Lester>And if it really is that, that platform
approach, this enables that direction.

232
00:14:43.030 --> 00:14:48.710
<v John Lester>How, how does that, how could that look
like for, for you, uh, if we start to find

233
00:14:48.710 --> 00:14:51.969
<v John Lester>those different partners, we start to find
those different contributors.

234
00:14:52.590 --> 00:14:56.869
<v John Lester>Is this what we need, that collaboration
to get us to the, to the end, let's call

235
00:14:56.869 --> 00:14:59.130
<v John Lester>it, or to get us on that next step onto
the train?

236
00:15:00.940 --> 00:15:01.489
<v Alisa>Absolutely.

237
00:15:01.549 --> 00:15:02.909
<v Alisa>I mean, it's all about openness.

238
00:15:02.950 --> 00:15:05.809
<v Alisa>It's all about collaboration, ecosystem
thinking.

239
00:15:07.070 --> 00:15:13.109
<v Alisa>That is how you really create value on top
of a platform approach, and I think this

240
00:15:13.109 --> 00:15:16.320
<v Alisa>is where the industry as a whole is, is,
is moving towards.

241
00:15:16.789 --> 00:15:19.510
<v Alisa>But in the end, it's all about the
business optimization.

242
00:15:19.630 --> 00:15:21.380
<v Alisa>So how can you actually create more.

243
00:15:22.039 --> 00:15:27.520
<v Alisa>Value for the business that's being run
within that building, whatever that business

244
00:15:27.520 --> 00:15:31.080
<v Alisa>might be, and I think, you know,
everything that's being done in terms of systems,

245
00:15:31.119 --> 00:15:37.039
<v Alisa>in terms of UX, in terms of workflows
needs to feed into those kind of measurable

246
00:15:37.039 --> 00:15:42.700
<v Alisa>KPIs that we are looking at, and then we
can actually call it a success in terms of

247
00:15:42.700 --> 00:15:43.219
<v Alisa>technology as well.

248
00:15:44.450 --> 00:15:48.719
<v John Lester>Yeah, and that's a, that's a great place
for us to finish today, I think, as you

249
00:15:48.719 --> 00:15:51.919
<v John Lester>say, it doesn't really matter what happens
from a technology perspective.

250
00:15:51.960 --> 00:15:54.090
<v John Lester>It doesn't matter what challenges are
overcome.

251
00:15:54.520 --> 00:15:59.080
<v John Lester>If the customer gets value, then this is a
step in the right direction.

252
00:15:59.229 --> 00:16:03.280
<v John Lester>And if that then is scalable and creates
more input impact, sorry, happy days.

253
00:16:03.799 --> 00:16:05.169
<v John Lester>Alisa, thanks so much for joining me.

254
00:16:05.330 --> 00:16:06.520
<v John Lester>Uh, it's always fun to chat.

255
00:16:06.770 --> 00:16:08.559
<v John Lester>I get the feeling we're going to have more
conversations.

256
00:16:08.609 --> 00:16:13.409
<v John Lester>I always say that, but, uh, but hey, here
you are back again after such a, a, a time

257
00:16:13.409 --> 00:16:13.650
<v John Lester>away.

258
00:16:13.809 --> 00:16:15.570
<v John Lester>So I, I hope that it's not the last time.

259
00:16:15.609 --> 00:16:18.789
<v John Lester>And thank you so much for, for lending us
your time and your knowledge today.

260
00:16:19.929 --> 00:16:22.510
<v Alisa>Looking forward to the next chat, John,
always a pleasure.

261
00:16:23.400 --> 00:16:24.080
<v John Lester>Bring it on.

262
00:16:24.390 --> 00:16:27.549
<v John Lester>Uh, and also thank you to everyone out
there who is listening.

263
00:16:27.710 --> 00:16:30.929
<v John Lester>Please remember to like, subscribe,
comment on this episode.

264
00:16:31.190 --> 00:16:33.349
<v John Lester>Look out for new episodes coming every
couple of weeks.

265
00:16:33.419 --> 00:16:37.229
<v John Lester>We're having a lot of great conversations
around artificial intelligence and

266
00:16:37.229 --> 00:16:41.229
<v John Lester>additional conversations like we've had
today with Alisa around how do we, how do we

267
00:16:41.229 --> 00:16:43.590
<v John Lester>get hold of this data and start to use it
more effectively.

268
00:16:43.669 --> 00:16:44.669
<v John Lester>So keep your eyes out for that.

269
00:16:44.710 --> 00:16:46.570
<v John Lester>And until then, we'll see you soon.
