WEBVTT
Language: en-US

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

2
00:00:12.710 --> 00:00:15.829
<v John Lester>My name is John Lester, and in this
episode we'll be talking about how data

3
00:00:15.829 --> 00:00:17.950
<v John Lester>analytics enables predictive maintenance.

4
00:00:18.280 --> 00:00:21.829
<v John Lester>I'm joined today by Tyson Suter, a global
business development manager for

5
00:00:21.829 --> 00:00:24.569
<v John Lester>digitalization at Siemens
Smart-Infrastructure.

6
00:00:25.069 --> 00:00:26.229
<v John Lester>Tyson, thanks for joining us.

7
00:00:26.319 --> 00:00:26.889
<v John Lester>Thanks John.

8
00:00:27.340 --> 00:00:31.030
<v John Lester>Give us an insight on how data analytics
enables predictive maintenance.

9
00:00:31.430 --> 00:00:36.549
<v Tyson Suter>So we, we talked many times about data
analytics and, and the benefits of it, but

10
00:00:36.549 --> 00:00:42.380
<v Tyson Suter>one of the biggest disruptors in our
market is saying, We do maintenance through a

11
00:00:42.380 --> 00:00:46.299
<v Tyson Suter>task-based system, so there's a couple of
options, it's either, uh, you know,

12
00:00:46.380 --> 00:00:51.220
<v Tyson Suter>reactive maintenance, meaning when
something breaks, let's go fix it, or uh

13
00:00:51.220 --> 00:00:53.689
<v Tyson Suter>preventative, meaning task-based
maintenance.

14
00:00:53.939 --> 00:00:57.740
<v Tyson Suter>Let's work through a list of items and,
and check to make sure everything's working.

15
00:00:57.860 --> 00:00:58.419
<v Tyson Suter>So this is

16
00:00:58.419 --> 00:00:59.540
<v John Lester>uh almost a schedule.

17
00:00:59.819 --> 00:01:04.169
<v Tyson Suter>Exactly, and this has been done for many
years, it it's, it's, it's what's expected,

18
00:01:04.500 --> 00:01:07.900
<v Tyson Suter>um, and there's really important things
that need to happen on as part of that

19
00:01:07.900 --> 00:01:08.500
<v Tyson Suter>maintenance.

20
00:01:08.860 --> 00:01:13.089
<v Tyson Suter>So, We're not talking about replacing
everything or or getting rid it all, we're

21
00:01:13.089 --> 00:01:18.459
<v Tyson Suter>saying let's let's see what's really
important and let's see what we can find and

22
00:01:18.459 --> 00:01:21.430
<v Tyson Suter>measure and and track with data analytics.

23
00:01:21.860 --> 00:01:27.260
<v Tyson Suter>So predictive maintenance is let's collect
all the data available uh available and

24
00:01:27.260 --> 00:01:29.680
<v Tyson Suter>say OK let's check if the sensors are
calibrated.

25
00:01:29.940 --> 00:01:32.260
<v Tyson Suter>Let's see if the actuators are driving
open and closed.

26
00:01:32.540 --> 00:01:35.360
<v Tyson Suter>Let's make sure that the smoke detector
systems are working.

27
00:01:35.760 --> 00:01:38.290
<v Tyson Suter>Let's see if doors are opening and closing
as expected.

28
00:01:38.599 --> 00:01:42.800
<v Tyson Suter>This is all checks that we can do with
data analytics, there's some really basic

29
00:01:42.800 --> 00:01:44.639
<v Tyson Suter>tasks that no longer required.

30
00:01:45.089 --> 00:01:49.519
<v Tyson Suter>And once you start doing that, you can
say, OK, let's let's not check the things

31
00:01:49.519 --> 00:01:50.419
<v Tyson Suter>that are working.

32
00:01:50.980 --> 00:01:54.860
<v Tyson Suter>Let's create a list of the stuff that we
know that's not working or we think could

33
00:01:54.860 --> 00:02:00.580
<v Tyson Suter>be near point of failure, going down in in
performance, so you can really create a

34
00:02:00.580 --> 00:02:05.889
<v Tyson Suter>list of tasks that are driven through data
where the individuals on site are saying,

35
00:02:05.940 --> 00:02:07.620
<v Tyson Suter>OK, I don't have to go and see if
something's working.

36
00:02:07.739 --> 00:02:10.860
<v Tyson Suter>I know something's not right here, the
data's telling me so.

37
00:02:11.250 --> 00:02:12.410
<v Tyson Suter>Let's go see what's happening.

38
00:02:12.729 --> 00:02:17.410
<v John Lester>So changing this, this maintenance
approach from reactive, like you mentioned,

39
00:02:17.570 --> 00:02:21.369
<v John Lester>fixing something when it breaks, from
having a schedule and changing things, which

40
00:02:21.369 --> 00:02:24.449
<v John Lester>could mean we're changing things that have
absolutely no issue and that we're

41
00:02:24.449 --> 00:02:29.330
<v John Lester>spending money where we don't need to, and
becoming proactive and understanding what

42
00:02:29.330 --> 00:02:34.089
<v John Lester>could happen in the near future or what is
not behaving how it should, and then

43
00:02:34.089 --> 00:02:35.270
<v John Lester>directing our efforts there.

44
00:02:35.570 --> 00:02:39.669
<v Tyson Suter>Exactly, and and as more we get more data
points every single day and, It it becomes

45
00:02:39.669 --> 00:02:44.070
<v Tyson Suter>more complex to maintain these systems, so
it's very important that we have digital

46
00:02:44.449 --> 00:02:46.660
<v Tyson Suter>services that can really solve these
problems.

47
00:02:46.949 --> 00:02:50.630
<v Tyson Suter>And when someone goes to a site, we wanna
give them as much information as possible

48
00:02:50.630 --> 00:02:54.869
<v Tyson Suter>so they can fix the issue straight away,
bring the right equipment, or even send the

49
00:02:54.869 --> 00:02:58.669
<v Tyson Suter>right resource to make sure that we're not
wasting time or people's money.

50
00:02:59.270 --> 00:03:03.100
<v John Lester>And this is an important point that you
touched on very quickly is we know that uh

51
00:03:03.399 --> 00:03:07.160
<v John Lester>devices are becoming more capable, we know
that systems are becoming more complex,

52
00:03:07.240 --> 00:03:10.880
<v John Lester>we know that more systems are talking and
working on the same networks and all these

53
00:03:10.880 --> 00:03:12.940
<v John Lester>sorts of things, so our buildings are
getting more complex.

54
00:03:14.110 --> 00:03:18.589
<v John Lester>If we took a traditional approach to
maintenance, then this very quickly becomes

55
00:03:18.589 --> 00:03:23.000
<v John Lester>untenable as far as the resources required
to deliver this, so we need predictive

56
00:03:23.000 --> 00:03:27.660
<v John Lester>maintenance, not just to improve what we
do today, but to actually absorb uh absorb

57
00:03:28.160 --> 00:03:30.839
<v John Lester>the stresses and the demands that we'll
have in the near future.

58
00:03:31.160 --> 00:03:34.789
<v Tyson Suter>Exactly, so just because we have more
sensors doesn't mean that they're going to be

59
00:03:34.789 --> 00:03:38.240
<v Tyson Suter>working, you know, even longer, they're
still gonna fail, so we really need to make

60
00:03:38.240 --> 00:03:42.779
<v Tyson Suter>sure that we can, Scale our solution to
enable these new technologies,

61
00:03:43.119 --> 00:03:46.199
<v John Lester>you also mentioned earlier something about
a workflow to make sure that when you go

62
00:03:46.199 --> 00:03:50.639
<v John Lester>to fix something, you have the right parts
already, so is this an aspect of, when

63
00:03:50.639 --> 00:03:53.130
<v John Lester>you have to go and do maintenance, you're
actually better prepared?

64
00:03:53.479 --> 00:03:57.880
<v Tyson Suter>Yeah, so you, when you, when you attend
site, you know exactly what type of

65
00:03:57.880 --> 00:03:58.910
<v Tyson Suter>equipment you're gonna be working on.

66
00:03:59.429 --> 00:04:03.190
<v Tyson Suter>If you have the data, you can say, OK, I
need, This looks like it's failed, clearly,

67
00:04:03.350 --> 00:04:04.589
<v Tyson Suter>let's bring a replacement.

68
00:04:04.789 --> 00:04:06.600
<v Tyson Suter>Like let's just do the work while I'm
there.

69
00:04:06.910 --> 00:04:11.580
<v Tyson Suter>It really reduces the amount of visits
required but also keeps everyone engaged.

70
00:04:11.949 --> 00:04:15.910
<v Tyson Suter>So that you can instantly deliver value,
you're solving problems straight away and

71
00:04:15.910 --> 00:04:18.829
<v Tyson Suter>then you're showing the value to the
customer, so they can really see the work

72
00:04:18.829 --> 00:04:19.190
<v Tyson Suter>you're doing.

73
00:04:19.600 --> 00:04:23.970
<v John Lester>And we spoke in the past about the
difference between data analytics and fault

74
00:04:23.970 --> 00:04:27.769
<v John Lester>detection, you know, when you, when you
receive a fault from a building that says

75
00:04:27.769 --> 00:04:31.769
<v John Lester>something has failed, there could be
multiple subsystems that are involved with that

76
00:04:31.769 --> 00:04:32.220
<v John Lester>fault.

77
00:04:32.690 --> 00:04:35.970
<v John Lester>So you don't know until you get there, so
by taking this data analytics approach,

78
00:04:36.049 --> 00:04:36.730
<v John Lester>you actually know.

79
00:04:36.834 --> 00:04:41.154
<v John Lester>What's happened leading up to the fault so
you can better determine what may have

80
00:04:41.154 --> 00:04:41.834
<v John Lester>caused the issue.

81
00:04:42.114 --> 00:04:46.385
<v Tyson Suter>Exactly, and then you can start really
pre-planning replacements and and and and

82
00:04:46.385 --> 00:04:51.234
<v Tyson Suter>keeping really critical parts on site so
you reduce that downtime, which is, which

83
00:04:51.234 --> 00:04:57.035
<v Tyson Suter>is critical, cos you don't want to be in a
position where, um, a missed issue or a a

84
00:04:57.035 --> 00:05:02.290
<v Tyson Suter>broken piece of equipment leads to, Uh,
uh, a company shutting down or a, a plant

85
00:05:02.290 --> 00:05:04.019
<v Tyson Suter>shutting down, which, which is quite
common, yeah,

86
00:05:04.100 --> 00:05:09.279
<v John Lester>a loss of productivity or, or a, um, an
interruption to service or whatever it might

87
00:05:09.279 --> 00:05:09.290
<v John Lester>be.

88
00:05:10.260 --> 00:05:11.130
<v John Lester>Wonderful, thank you,

89
00:05:11.290 --> 00:05:11.700
<v Tyson Suter>thanks, John.

90
00:05:12.559 --> 00:05:15.609
<v John Lester>And thank you all for joining us here on
Buildings of Tomorrow, please comment,

91
00:05:15.809 --> 00:05:20.130
<v John Lester>share and like this episode and also
ensure to subscribe to us here on this channel.

92
00:05:20.290 --> 00:05:21.170
<v John Lester>We'll see you again soon.
