WEBVTT

1
00:00:00.080 --> 00:00:03.319
<v Speaker 1>Welcome to the deep dive. Today, we're venturing into the

2
00:00:03.359 --> 00:00:09.320
<v Speaker 1>fascinating realm of radio frequency identification or RFID and it's

3
00:00:09.359 --> 00:00:12.320
<v Speaker 1>close relatives in the world of autoid technologies.

4
00:00:12.400 --> 00:00:14.400
<v Speaker 2>That's right, we've gathered quite a bit of information. We're

5
00:00:14.400 --> 00:00:16.920
<v Speaker 2>going to explore their origins, how they work, some really

6
00:00:16.960 --> 00:00:18.839
<v Speaker 2>diverse applications across industries.

7
00:00:19.039 --> 00:00:22.800
<v Speaker 1>Yeah, things like standardization efforts, the economic side, security which

8
00:00:22.839 --> 00:00:26.600
<v Speaker 1>is huge, and even looking a bit into the future

9
00:00:26.640 --> 00:00:27.760
<v Speaker 1>potential exactly.

10
00:00:27.839 --> 00:00:31.199
<v Speaker 2>Think of this as your fast track understanding how these

11
00:00:31.320 --> 00:00:36.079
<v Speaker 2>often well invisible technologies are fundamentally changing things, everything from

12
00:00:36.200 --> 00:00:38.280
<v Speaker 2>products you buy to healthcare.

13
00:00:38.439 --> 00:00:41.520
<v Speaker 1>So for you, our listener, the learner, the goal here

14
00:00:41.719 --> 00:00:46.759
<v Speaker 1>is a comprehensive but hopefully easily digestible understanding of RFID

15
00:00:46.880 --> 00:00:47.679
<v Speaker 1>and auto ID.

16
00:00:47.920 --> 00:00:51.039
<v Speaker 2>We want to illuminate the core ideas, highlight some maybe

17
00:00:51.079 --> 00:00:54.719
<v Speaker 2>surprising real world uses, and really dig into why they're

18
00:00:54.759 --> 00:00:55.719
<v Speaker 2>becoming so important.

19
00:00:55.759 --> 00:00:58.000
<v Speaker 1>And our sources cover quite a bit the technical basics,

20
00:00:58.079 --> 00:01:02.000
<v Speaker 1>practical uses in automotive logis, sticks, healthcare, aviation.

21
00:01:02.039 --> 00:01:06.439
<v Speaker 2>HM and those crucial bits about standards, security, the economics,

22
00:01:06.480 --> 00:01:07.439
<v Speaker 2>and where it's all heading.

23
00:01:07.719 --> 00:01:10.400
<v Speaker 1>Okay, let's start by unpacking the basics. What exactly is

24
00:01:10.519 --> 00:01:11.879
<v Speaker 1>our FID well.

25
00:01:12.040 --> 00:01:17.000
<v Speaker 2>Our sources describe it as enabling contactless identification of objects

26
00:01:17.680 --> 00:01:22.079
<v Speaker 2>using these electronically writable data carriers, almost like a digital label.

27
00:01:22.159 --> 00:01:23.920
<v Speaker 2>You don't need to see your touch, right.

28
00:01:23.959 --> 00:01:26.439
<v Speaker 1>And the amazing part is it does this reliably at

29
00:01:26.480 --> 00:01:30.200
<v Speaker 1>low cost and over distances well sometimes several meters.

30
00:01:30.280 --> 00:01:31.079
<v Speaker 3>It's pretty opressive.

31
00:01:31.200 --> 00:01:34.719
<v Speaker 2>The initial vision was quite ambitious, you know, even talking

32
00:01:34.719 --> 00:01:38.640
<v Speaker 2>about the Internet of things way back, imagining intelligent refrigerators

33
00:01:38.640 --> 00:01:40.040
<v Speaker 2>managing your shopping.

34
00:01:39.680 --> 00:01:42.480
<v Speaker 1>List seems like science fiction back done. But you know,

35
00:01:42.599 --> 00:01:45.120
<v Speaker 1>the idea of contactless radio idea, it's actually been used

36
00:01:45.159 --> 00:01:47.040
<v Speaker 1>industrially for a while, hasn't it It has?

37
00:01:47.159 --> 00:01:50.959
<v Speaker 2>Yeah, One source points out Siemens introduced their first industrial

38
00:01:51.000 --> 00:01:54.439
<v Speaker 2>system MOBM, maybe twenty five years before the source was written,

39
00:01:54.840 --> 00:01:56.319
<v Speaker 2>so roughly nineteen eighty three.

40
00:01:56.400 --> 00:01:58.799
<v Speaker 1>Wow, eighty three. And how good was it back then?

41
00:01:58.879 --> 00:01:59.120
<v Speaker 3>Did this?

42
00:01:59.159 --> 00:02:02.120
<v Speaker 2>It's initial regate was just forty milimeters.

43
00:02:01.599 --> 00:02:04.680
<v Speaker 1>Forty milimeters that's tiny, less than my thumb with.

44
00:02:04.879 --> 00:02:08.599
<v Speaker 2>Exactly, But even then it could store sixty four bites

45
00:02:08.599 --> 00:02:11.639
<v Speaker 2>of data, which you know, was something. Just it shows

46
00:02:11.639 --> 00:02:14.639
<v Speaker 2>how far we've come with RFID now used successfully just

47
00:02:14.680 --> 00:02:15.599
<v Speaker 2>about everywhere.

48
00:02:15.919 --> 00:02:20.039
<v Speaker 1>Okay, so RFID isn't brand new, despite feeling cutting edge sometimes,

49
00:02:20.080 --> 00:02:23.039
<v Speaker 1>but it does have competition, right the good old barcode.

50
00:02:23.080 --> 00:02:26.319
<v Speaker 2>Absolutely, barcodes someth might think they're outdated now, but they

51
00:02:26.319 --> 00:02:28.879
<v Speaker 2>were actually being rolled out commercially around the same time

52
00:02:29.199 --> 00:02:31.159
<v Speaker 2>as those early RFID systems.

53
00:02:31.240 --> 00:02:33.479
<v Speaker 1>Oh really, I didn't realize the timelines were that close.

54
00:02:33.680 --> 00:02:36.719
<v Speaker 2>Yeah, there's that fun fact about Wrigley's chewing gum being

55
00:02:36.759 --> 00:02:40.000
<v Speaker 2>the first barcode scanned product at a checkout back in

56
00:02:40.039 --> 00:02:40.680
<v Speaker 2>seventy four.

57
00:02:40.879 --> 00:02:44.599
<v Speaker 1>Ah, Wriggly's gum and then standards like the EAN, the

58
00:02:44.639 --> 00:02:47.680
<v Speaker 1>European article number that really helped them take off, didn't

59
00:02:47.680 --> 00:02:50.840
<v Speaker 1>it that A source calls it in an exorable triumphal march.

60
00:02:50.960 --> 00:02:52.479
<v Speaker 3>It really did solidify their place.

61
00:02:52.560 --> 00:02:55.520
<v Speaker 2>And interestingly, the first US patent for a barcode was

62
00:02:55.599 --> 00:02:59.400
<v Speaker 2>even earlier nineteen forty nine, so maybe a slightly faster

63
00:02:59.479 --> 00:03:02.400
<v Speaker 2>path to hert than the very first industrial RFID.

64
00:03:02.560 --> 00:03:05.080
<v Speaker 1>The barcodes aren't the only optical competitor now. We have

65
00:03:05.080 --> 00:03:06.560
<v Speaker 1>two D matrix codes too.

66
00:03:06.800 --> 00:03:12.159
<v Speaker 2>Exactly, and the source emphasizes that these optical methods, especially

67
00:03:12.159 --> 00:03:15.960
<v Speaker 2>two D matrix codes, still have real advantages. They can

68
00:03:16.199 --> 00:03:19.520
<v Speaker 2>justifiably compete with RFID in certain situations.

69
00:03:19.520 --> 00:03:22.919
<v Speaker 1>Okay, so what makes these two d codes still relevant?

70
00:03:22.919 --> 00:03:24.000
<v Speaker 1>What are their strengths?

71
00:03:24.240 --> 00:03:27.000
<v Speaker 2>Well, several things. They need less physical space, which is

72
00:03:27.000 --> 00:03:30.120
<v Speaker 2>great for small items. They simplify reading because you can

73
00:03:30.120 --> 00:03:32.759
<v Speaker 2>scan them from any direction omnidirectional reading.

74
00:03:32.599 --> 00:03:35.840
<v Speaker 1>Ah okay, no need to line it up perfectly, and they.

75
00:03:35.680 --> 00:03:39.560
<v Speaker 2>Handle low contrast better. Plus, they store way more data

76
00:03:39.599 --> 00:03:42.159
<v Speaker 2>than a traditional barcode, and they have built in error

77
00:03:42.240 --> 00:03:45.439
<v Speaker 2>correction making them more reliable error correction. That sounds important,

78
00:03:45.520 --> 00:03:48.879
<v Speaker 2>it is. And there's this technique direct part marking DPM.

79
00:03:49.039 --> 00:03:51.319
<v Speaker 2>You can put the code directly onto the part itself

80
00:03:51.439 --> 00:03:52.879
<v Speaker 2>like etching it on yeah.

81
00:03:52.719 --> 00:03:53.520
<v Speaker 3>Or laser marking.

82
00:03:53.719 --> 00:03:56.520
<v Speaker 2>It makes it super durable, survives harsh conditions, and you

83
00:03:56.599 --> 00:03:57.800
<v Speaker 2>save on the cost of labels.

84
00:03:57.879 --> 00:04:01.800
<v Speaker 1>Okay, that makes sense. So barcodes two decodes. But let's

85
00:04:01.800 --> 00:04:05.159
<v Speaker 1>circle back and really dig into rfid's technical side. What

86
00:04:05.280 --> 00:04:06.919
<v Speaker 1>are the basic building blocks?

87
00:04:07.199 --> 00:04:07.479
<v Speaker 3>Okay?

88
00:04:07.520 --> 00:04:10.479
<v Speaker 2>So an RFID system at its heart has two main

89
00:04:10.520 --> 00:04:13.759
<v Speaker 2>things transponders you probably know them as tags, right the tags,

90
00:04:13.960 --> 00:04:17.920
<v Speaker 2>and reading devices or readers. These readers need to connect

91
00:04:18.160 --> 00:04:20.920
<v Speaker 2>to the bigger IT systems obviously to share the data.

92
00:04:21.319 --> 00:04:23.959
<v Speaker 2>They use various interfaces for that serial like RS two

93
00:04:24.000 --> 00:04:27.360
<v Speaker 2>three D two Ethernet both standard and industrial versions, even

94
00:04:27.360 --> 00:04:28.920
<v Speaker 2>digital inputs to trigger a read.

95
00:04:29.199 --> 00:04:32.800
<v Speaker 1>And the actual wireless communication between the reader and the tag.

96
00:04:32.879 --> 00:04:34.560
<v Speaker 1>How does that magic happen?

97
00:04:34.680 --> 00:04:39.120
<v Speaker 2>That happens over the air interface. It's basically the set

98
00:04:39.160 --> 00:04:42.120
<v Speaker 2>of rules and protocols for how they talk wirelessly, the

99
00:04:42.199 --> 00:04:45.360
<v Speaker 2>commands they exchange, and these are often scannedized so different

100
00:04:45.399 --> 00:04:46.920
<v Speaker 2>manufacturers gear can work together.

101
00:04:47.000 --> 00:04:49.959
<v Speaker 1>The interoperability is key, I imagine absolutely, And there's a

102
00:04:50.040 --> 00:04:51.319
<v Speaker 1>huge variety of transponders.

103
00:04:51.360 --> 00:04:55.000
<v Speaker 2>I mean, from big tough, heat resistant industrial tags. Our

104
00:04:55.079 --> 00:04:58.439
<v Speaker 2>source shows one the MDSU five eighty nine, down to

105
00:04:58.519 --> 00:05:01.480
<v Speaker 2>these tiny pill tags you can bed right into metal tools.

106
00:05:01.560 --> 00:05:05.120
<v Speaker 1>Wow, embed in metal. That's impressive. What about power? Those

107
00:05:05.160 --> 00:05:06.680
<v Speaker 1>tiny tags can't have batteries?

108
00:05:06.759 --> 00:05:11.199
<v Speaker 2>Surely you got it. Most are passive no battery. That

109
00:05:11.279 --> 00:05:15.439
<v Speaker 2>means they're simpler, cheaper, last, practically forever, can be incredibly

110
00:05:15.480 --> 00:05:19.639
<v Speaker 2>small and potentially cost like less than ten eurocents each less.

111
00:05:19.480 --> 00:05:22.040
<v Speaker 1>Than ten cents. So how do they work without power?

112
00:05:22.199 --> 00:05:25.439
<v Speaker 2>They harvest energy from the reader's signal. Depends on the frequency,

113
00:05:25.720 --> 00:05:26.879
<v Speaker 2>but there are two main ways.

114
00:05:26.959 --> 00:05:30.439
<v Speaker 1>Okay, let's break those down. Inductive coupling LF and HF ranges.

115
00:05:30.519 --> 00:05:33.199
<v Speaker 2>Right, that's an older method. Works like a transformer. The

116
00:05:33.240 --> 00:05:37.279
<v Speaker 2>reader sends power through its antenna coil, creating a magnetic field. Okay,

117
00:05:37.360 --> 00:05:40.279
<v Speaker 2>the tag has a coil too. When it enters the field,

118
00:05:40.439 --> 00:05:43.959
<v Speaker 2>a voltage is induced in its coil. It rectifies that voltage,

119
00:05:44.120 --> 00:05:45.600
<v Speaker 2>powers up its little chip.

120
00:05:45.439 --> 00:05:47.439
<v Speaker 1>Clever and sending data back.

121
00:05:47.639 --> 00:05:51.120
<v Speaker 2>It uses something called load modulation. Basically, it changes how

122
00:05:51.120 --> 00:05:54.000
<v Speaker 2>its antenna draws power slightly, and the reader detects that

123
00:05:54.040 --> 00:05:57.160
<v Speaker 2>tiny change in the field. Common frequencies are one hundred

124
00:05:57.160 --> 00:06:01.000
<v Speaker 2>and twenty five kilohertz that's LF low frequency and thirteen

125
00:06:01.040 --> 00:06:03.879
<v Speaker 2>point five to six megahertz HF or high frequency.

126
00:06:04.120 --> 00:06:05.959
<v Speaker 1>And the benefit of those frequencies.

127
00:06:05.560 --> 00:06:08.240
<v Speaker 2>They're pretty much usable worldwide without heavy restrictions, and you

128
00:06:08.240 --> 00:06:10.720
<v Speaker 2>can get decent red ranges, maybe over meter, though you

129
00:06:10.759 --> 00:06:12.439
<v Speaker 2>often need larger antennas for that.

130
00:06:12.680 --> 00:06:16.519
<v Speaker 1>Okay, harvesting energy from the magnetic field, got it. What's

131
00:06:16.560 --> 00:06:19.360
<v Speaker 1>the other main method for passive tags? You mentioned UHF

132
00:06:19.480 --> 00:06:20.839
<v Speaker 1>electromagnetic coupling.

133
00:06:20.839 --> 00:06:26.120
<v Speaker 2>Exactly UAHF ultra high frequency. Unlike LFAHF, which is mostly magnetic,

134
00:06:26.480 --> 00:06:30.839
<v Speaker 2>UHF uses true electromagnetic waves, both electric and magnetic fields.

135
00:06:31.240 --> 00:06:35.160
<v Speaker 2>This allows for much longer ranges, think five meters, maybe even.

136
00:06:35.000 --> 00:06:35.839
<v Speaker 1>More five meters.

137
00:06:35.839 --> 00:06:39.000
<v Speaker 2>That's a big difference, it is, but it generally needs

138
00:06:39.040 --> 00:06:42.160
<v Speaker 2>higher transmission power from the radar, and those power levels

139
00:06:42.199 --> 00:06:45.759
<v Speaker 2>are regulated differently in different regions. The tags typically use

140
00:06:45.759 --> 00:06:49.399
<v Speaker 2>simple dipole antennas to grab that energy. Low power consumption

141
00:06:49.480 --> 00:06:51.720
<v Speaker 2>in the tag chip is absolutely critical.

142
00:06:51.720 --> 00:06:54.279
<v Speaker 1>Here makes sense. And the last one mentioned is NFC

143
00:06:54.360 --> 00:06:56.480
<v Speaker 1>in your field communication? How does that fit in?

144
00:06:56.680 --> 00:06:59.839
<v Speaker 2>NFC also uses the magnetic field part like HF, but

145
00:07:00.040 --> 00:07:03.000
<v Speaker 2>it's specifically designed for very short ranges, just a few

146
00:07:03.000 --> 00:07:03.959
<v Speaker 2>decimeters max.

147
00:07:04.160 --> 00:07:06.040
<v Speaker 1>Like tapping your phone to pay precisely.

148
00:07:06.560 --> 00:07:08.560
<v Speaker 2>The trade off for the short range is simplicity and

149
00:07:08.639 --> 00:07:11.920
<v Speaker 2>optimized antennas, perfect for those close proximity interactions.

150
00:07:12.160 --> 00:07:15.079
<v Speaker 1>Okay, so a whole family of related technologies for different needs.

151
00:07:15.519 --> 00:07:17.879
<v Speaker 1>Now we talked about two D codes being still relevant.

152
00:07:18.240 --> 00:07:21.040
<v Speaker 1>Let's look closer at the structure of a data matrix code.

153
00:07:21.079 --> 00:07:24.240
<v Speaker 2>Sure got a distinct look. There's the data area in

154
00:07:24.279 --> 00:07:27.360
<v Speaker 2>the middle, then around that an alternating black and white border,

155
00:07:27.439 --> 00:07:29.959
<v Speaker 2>and then a solid border the finder pattern.

156
00:07:30.040 --> 00:07:32.240
<v Speaker 1>The finder pattern helps the reader locate.

157
00:07:31.959 --> 00:07:34.879
<v Speaker 2>It exactly, helps it orient itself crucial and what.

158
00:07:34.839 --> 00:07:39.399
<v Speaker 1>About damage, scratches, dirt. How do they cope compared to

159
00:07:39.439 --> 00:07:40.480
<v Speaker 1>a simple bar code.

160
00:07:40.560 --> 00:07:43.839
<v Speaker 2>That's where they're built in. Error correction shines. ECC two

161
00:07:43.920 --> 00:07:46.600
<v Speaker 2>hundred is the standard. It means the code can often

162
00:07:46.639 --> 00:07:48.600
<v Speaker 2>still be read even if part of it is damaged

163
00:07:48.680 --> 00:07:51.879
<v Speaker 2>or missing, up to about twenty eight percent damage typically

164
00:07:52.000 --> 00:07:52.879
<v Speaker 2>twenty eight percent.

165
00:07:52.920 --> 00:07:54.399
<v Speaker 1>That's pretty robust, it is.

166
00:07:54.800 --> 00:07:57.279
<v Speaker 2>They also support different coding schemes, pack a lot of

167
00:07:57.279 --> 00:07:59.920
<v Speaker 2>info into a small space, and can even mimic old

168
00:08:00.160 --> 00:08:03.839
<v Speaker 2>barcode standards like EA N one twenty eight. The read

169
00:08:03.959 --> 00:08:06.800
<v Speaker 2>Solomon algorithm they use is really good at fixing errors,

170
00:08:06.920 --> 00:08:09.519
<v Speaker 2>even burst errors like esscratch across the code.

171
00:08:09.600 --> 00:08:12.240
<v Speaker 1>Impressive resilience, anything else structurally important?

172
00:08:12.600 --> 00:08:12.879
<v Speaker 3>Yeah?

173
00:08:12.920 --> 00:08:16.600
<v Speaker 2>The quiet zone standards require a clear margin around the code,

174
00:08:16.920 --> 00:08:20.040
<v Speaker 2>usually at least one cell wide helps three to separate

175
00:08:20.040 --> 00:08:23.040
<v Speaker 2>the code from the background, and size wise they range

176
00:08:23.040 --> 00:08:25.879
<v Speaker 2>from tiny ten by ten cells up to one four

177
00:08:26.000 --> 00:08:29.199
<v Speaker 2>by one four, but most common ones are smaller, maybe

178
00:08:29.279 --> 00:08:30.639
<v Speaker 2>up to forty eight by forty eight.

179
00:08:30.800 --> 00:08:35.840
<v Speaker 1>Okay, Now, putting these codes onto things labels versus direct marking,

180
00:08:36.279 --> 00:08:37.919
<v Speaker 1>what are the trade offs with labels?

181
00:08:38.039 --> 00:08:41.320
<v Speaker 2>Labels usually give you better print quality, higher contrast, that

182
00:08:41.320 --> 00:08:44.080
<v Speaker 2>can make the reading easier, maybe allowing for cheaper readers.

183
00:08:44.320 --> 00:08:47.399
<v Speaker 2>Plus you're not messing with the object's material itself. But

184
00:08:47.559 --> 00:08:51.559
<v Speaker 2>the downside cost potentially, especially if you need really durable

185
00:08:51.600 --> 00:08:55.320
<v Speaker 2>labels for harsh environments, they can get expensive, particularly in

186
00:08:55.360 --> 00:08:58.440
<v Speaker 2>high volumes. That's when the direct marking starts looking attractive.

187
00:08:58.559 --> 00:09:01.240
<v Speaker 1>Right, skip the label cost, but you mentioned things to

188
00:09:01.320 --> 00:09:02.960
<v Speaker 1>watch out for with direct marking.

189
00:09:03.159 --> 00:09:05.600
<v Speaker 2>Definitely, First, you have to consider if the marking process

190
00:09:05.600 --> 00:09:08.000
<v Speaker 2>itself could damage the part, especially if it's thin or

191
00:09:08.080 --> 00:09:10.440
<v Speaker 2>under stress. You wouldn't want to weaken it makes sense,

192
00:09:10.559 --> 00:09:13.279
<v Speaker 2>and the material itself has to be suitable for the

193
00:09:13.320 --> 00:09:16.559
<v Speaker 2>marking method you choose to get a clear, lasting mark.

194
00:09:17.000 --> 00:09:17.799
<v Speaker 3>There are various ways.

195
00:09:17.919 --> 00:09:22.120
<v Speaker 2>Laser marking is common, with different techniques like etching, oblation, tempering.

196
00:09:22.320 --> 00:09:26.480
<v Speaker 1>Laser marking sounds flexible but maybe expensive upfront.

197
00:09:26.600 --> 00:09:29.840
<v Speaker 2>It can be, yeah, but methods like color change lasers

198
00:09:29.879 --> 00:09:32.399
<v Speaker 2>just heat the material slightly to make a mark. Good

199
00:09:32.399 --> 00:09:35.440
<v Speaker 2>for sterile environments, though, you need to consider if the

200
00:09:35.480 --> 00:09:38.399
<v Speaker 2>part will see more heat later, which could affect the

201
00:09:38.440 --> 00:09:39.399
<v Speaker 2>mark's longevity.

202
00:09:39.679 --> 00:09:42.519
<v Speaker 1>So careful choices needed based on the part and its

203
00:09:42.600 --> 00:09:45.320
<v Speaker 1>life cycle, and once the codes are on there, what

204
00:09:45.440 --> 00:09:47.360
<v Speaker 1>reads them? What makes up a reading system.

205
00:09:47.480 --> 00:09:50.919
<v Speaker 2>A typical two D reader has a camera unit, lens, sensor,

206
00:09:51.399 --> 00:09:54.799
<v Speaker 2>image capture stuff. It needs lighting, often built in LEDs.

207
00:09:55.159 --> 00:09:58.320
<v Speaker 2>There's a controller for processing the image and communicating, and

208
00:09:58.360 --> 00:10:00.240
<v Speaker 2>then the housing and connections.

209
00:10:00.000 --> 00:10:02.720
<v Speaker 1>Please vary a lot depending on the job hugely.

210
00:10:03.399 --> 00:10:06.080
<v Speaker 2>Think of a fixed scanner on a fast production line

211
00:10:06.240 --> 00:10:09.159
<v Speaker 2>versus a handheld scanner and a warehouse. Even the fixed

212
00:10:09.200 --> 00:10:12.480
<v Speaker 2>ones range from compact all in one units to more

213
00:10:12.519 --> 00:10:15.519
<v Speaker 2>modular systems where you can pick specific lights and lenses

214
00:10:15.519 --> 00:10:18.559
<v Speaker 2>for tricky reads, maybe connect via different industrial networks. Some

215
00:10:18.679 --> 00:10:21.639
<v Speaker 2>are basic for high contrast labels, others are built to

216
00:10:21.639 --> 00:10:24.600
<v Speaker 2>handle tough direct part marks in automotive or aerospace.

217
00:10:25.200 --> 00:10:29.720
<v Speaker 1>Okay, so tags, codes, readers, scanners, But none of this

218
00:10:29.799 --> 00:10:30.639
<v Speaker 1>works in isolation.

219
00:10:30.840 --> 00:10:31.039
<v Speaker 3>Right.

220
00:10:31.519 --> 00:10:34.360
<v Speaker 1>How does it all plug into a company's bigger IT picture?

221
00:10:34.559 --> 00:10:37.240
<v Speaker 2>That's a crucial point. Putting an autoid isn't just a

222
00:10:37.279 --> 00:10:41.600
<v Speaker 2>local fix. It always means changes to it processes, data management. Often,

223
00:10:41.679 --> 00:10:44.519
<v Speaker 2>especially in logistics, it goes beyond the company walls, integrating

224
00:10:44.559 --> 00:10:45.799
<v Speaker 2>with suppliers.

225
00:10:45.279 --> 00:10:47.559
<v Speaker 1>Customers, so it ripple effects through the whole system.

226
00:10:47.600 --> 00:10:48.159
<v Speaker 3>Absolutely.

227
00:10:48.279 --> 00:10:50.480
<v Speaker 2>Now, if you're just swapping barcodes for two D codes,

228
00:10:50.519 --> 00:10:52.879
<v Speaker 2>maybe existing connections like RS two three two or USB

229
00:10:53.039 --> 00:10:55.840
<v Speaker 2>or fine if readers plug into PCs. But in serious

230
00:10:55.879 --> 00:11:00.480
<v Speaker 2>industrial settings you're usually looking at industrial networks industrial Ethernet, FABUS,

231
00:11:00.519 --> 00:11:05.279
<v Speaker 2>DP PROFILA connecting those readers. Industrial Ethernet is often preferred

232
00:11:05.320 --> 00:11:08.039
<v Speaker 2>for handling lots of data like images.

233
00:11:07.799 --> 00:11:10.559
<v Speaker 1>And the main goal is always reliable data.

234
00:11:10.279 --> 00:11:13.639
<v Speaker 2>Capture, fast and fault free. That's the aim. And in

235
00:11:13.759 --> 00:11:16.519
<v Speaker 2>industry or logistics, it's usually better to get a no

236
00:11:16.679 --> 00:11:20.519
<v Speaker 2>read signal and error maybe need manual intervention, than to

237
00:11:20.519 --> 00:11:23.679
<v Speaker 2>get a wrong read that goes unnoticed and messes things

238
00:11:23.759 --> 00:11:24.480
<v Speaker 2>up downstream.

239
00:11:24.639 --> 00:11:27.000
<v Speaker 1>Makes sense. A bad read is worse than no read.

240
00:11:27.159 --> 00:11:29.840
<v Speaker 1>So what does the typical IT architecture look like.

241
00:11:30.080 --> 00:11:30.720
<v Speaker 3>It's layered.

242
00:11:31.200 --> 00:11:33.639
<v Speaker 2>You've got the tags or codes at the bottom, then

243
00:11:33.679 --> 00:11:37.440
<v Speaker 2>the readers talking to them. Often readers connect to edge servers.

244
00:11:37.519 --> 00:11:39.960
<v Speaker 2>These can do some local processing, maybe run some business.

245
00:11:39.799 --> 00:11:41.039
<v Speaker 3>Logic right now, and computing.

246
00:11:41.080 --> 00:11:43.759
<v Speaker 2>Then you often have middleware. Its job is secure data

247
00:11:43.759 --> 00:11:48.159
<v Speaker 2>distribution across the network. Above that the big ERP systems

248
00:11:48.279 --> 00:11:51.960
<v Speaker 2>enterprise resource planning, holding the main business data and logic,

249
00:11:52.279 --> 00:11:56.080
<v Speaker 2>and finally client applications, the user interfaces people work with.

250
00:11:56.600 --> 00:11:59.320
<v Speaker 1>Where does the RFID specific data live.

251
00:11:59.639 --> 00:12:03.159
<v Speaker 2>Sometimes times there are dedicated RFID repositories, maybe between the

252
00:12:03.360 --> 00:12:06.480
<v Speaker 2>ERP and of EDG servers for performance reasons or linking

253
00:12:06.480 --> 00:12:10.480
<v Speaker 2>to external systems. And nowadays some RFID readers are intelligent

254
00:12:10.600 --> 00:12:13.639
<v Speaker 2>enough to run some of that edge software themselves.

255
00:12:13.639 --> 00:12:17.759
<v Speaker 1>Interesting and communication between all these layers, these transparent interfaces.

256
00:12:17.879 --> 00:12:21.879
<v Speaker 2>Yeah, but critically that air interface between reader and tag

257
00:12:22.639 --> 00:12:27.399
<v Speaker 2>that really benefits from standardization for interoperability, mixing and matching

258
00:12:27.399 --> 00:12:28.559
<v Speaker 2>hardware becomes possible.

259
00:12:28.639 --> 00:12:32.159
<v Speaker 1>Okay, a complex architecture. What about the actual data flowing

260
00:12:32.159 --> 00:12:34.240
<v Speaker 1>through it? What's being captured and managed?

261
00:12:34.360 --> 00:12:36.919
<v Speaker 2>Well, you start with object description data from the ERP.

262
00:12:37.120 --> 00:12:41.159
<v Speaker 2>What the thing is? It's properties relationships that gets linked

263
00:12:41.200 --> 00:12:44.840
<v Speaker 2>to a unique id UID when the tag is initialized

264
00:12:44.919 --> 00:12:46.480
<v Speaker 2>or the code is generated.

265
00:12:46.080 --> 00:12:48.159
<v Speaker 1>So identifying the what exactly.

266
00:12:48.480 --> 00:12:53.200
<v Speaker 2>Then every time it's read, you capture tracking data, timestamp, location,

267
00:12:54.000 --> 00:12:57.519
<v Speaker 2>That UID plus time and location forms a basic tracking event.

268
00:12:58.000 --> 00:13:00.000
<v Speaker 2>Sometimes this can even be stored on the tag itself.

269
00:13:00.080 --> 00:13:00.919
<v Speaker 1>Beyond just location.

270
00:13:01.159 --> 00:13:03.960
<v Speaker 2>Oh yeah, ambient data maybe temperature from a sensor. Tag

271
00:13:04.200 --> 00:13:05.960
<v Speaker 2>process data, what steps it in?

272
00:13:05.960 --> 00:13:07.679
<v Speaker 3>Why was it read? Who read it? That might come

273
00:13:07.720 --> 00:13:09.159
<v Speaker 3>from system settings or a user.

274
00:13:09.000 --> 00:13:11.320
<v Speaker 1>Input, and all this raw data lets you figure out

275
00:13:11.360 --> 00:13:12.960
<v Speaker 1>more complex things.

276
00:13:12.720 --> 00:13:15.879
<v Speaker 2>Right, you can derive things like how long something sat somewhere,

277
00:13:15.919 --> 00:13:20.279
<v Speaker 2>stopping time, total time through a process, throughput time, direction

278
00:13:20.440 --> 00:13:23.519
<v Speaker 2>of travel, even identifying groups of items read together.

279
00:13:23.799 --> 00:13:26.639
<v Speaker 1>That's a lot of potential insight. How do you handle

280
00:13:26.679 --> 00:13:29.039
<v Speaker 1>problems If a reader isn't working right?

281
00:13:29.480 --> 00:13:34.039
<v Speaker 2>Error diagnosis is key log files error handling usually managed

282
00:13:34.039 --> 00:13:36.759
<v Speaker 2>at the edge server level, so you can analyze problems remotely.

283
00:13:37.120 --> 00:13:40.399
<v Speaker 2>You need to be able to trace what happened in context.

284
00:13:39.960 --> 00:13:42.000
<v Speaker 1>And monitoring the system itself essential.

285
00:13:42.399 --> 00:13:45.919
<v Speaker 2>Keeping an eye on edge server health, CPU memory, read rates,

286
00:13:46.080 --> 00:13:50.440
<v Speaker 2>device reliability. That's crucial for maintaining quality service or QoS.

287
00:13:50.759 --> 00:13:54.080
<v Speaker 1>So building these systems requires thinking beyond just the readers

288
00:13:54.080 --> 00:13:57.360
<v Speaker 1>and tags. What other big architectural principles are important?

289
00:13:57.440 --> 00:13:57.919
<v Speaker 3>Security?

290
00:13:58.000 --> 00:14:02.840
<v Speaker 2>Obviously, availability you needed running, extendability for future needs, and

291
00:14:03.000 --> 00:14:05.200
<v Speaker 2>adaptability being able to integrate new tech.

292
00:14:05.279 --> 00:14:06.600
<v Speaker 1>How do you ensure availability?

293
00:14:06.720 --> 00:14:12.120
<v Speaker 2>Redundancy helps backup devices servers? Secure communication Edge servers should

294
00:14:12.159 --> 00:14:15.279
<v Speaker 2>ideally have some offline capability store data locally if the

295
00:14:15.360 --> 00:14:18.879
<v Speaker 2>network drops, then sync up later, and the software running

296
00:14:18.919 --> 00:14:21.679
<v Speaker 2>on the edge needs to be fult colerant.

297
00:14:21.279 --> 00:14:23.360
<v Speaker 1>And extendability, adaptability.

298
00:14:23.639 --> 00:14:27.759
<v Speaker 2>Open interfaces are vital plug and play capabilities. Businesses change

299
00:14:28.080 --> 00:14:31.799
<v Speaker 2>needs evolve. You might want to switch RFID frequencies, use

300
00:14:31.799 --> 00:14:35.960
<v Speaker 2>different tag vendors, integrate a new protocol. The architecture shouldn't

301
00:14:36.000 --> 00:14:39.200
<v Speaker 2>lock you in. It should be flexible, configurable definitely.

302
00:14:39.279 --> 00:14:42.279
<v Speaker 1>Sounds like forward planning is essential. Now we've talked about

303
00:14:42.279 --> 00:14:45.399
<v Speaker 1>both RFID and two D codes, how does a company

304
00:14:45.440 --> 00:14:47.879
<v Speaker 1>actually choose between them for a specific job.

305
00:14:48.159 --> 00:14:50.360
<v Speaker 2>It really comes down to the specifics of the application.

306
00:14:50.679 --> 00:14:54.919
<v Speaker 2>What are the environmental conditions, heat, moisture, dirt, What redistance

307
00:14:54.960 --> 00:14:57.480
<v Speaker 2>do you need? How fast are the objects moving? What's

308
00:14:57.519 --> 00:14:59.720
<v Speaker 2>the object made of? How much space is there for

309
00:14:59.759 --> 00:15:02.120
<v Speaker 2>a time or code? How does it need to integrate?

310
00:15:02.200 --> 00:15:04.919
<v Speaker 1>Give me some typical strengths. When does RFID usually win.

311
00:15:05.320 --> 00:15:08.159
<v Speaker 2>RFID often excels when you need to read things on

312
00:15:08.200 --> 00:15:11.639
<v Speaker 2>the move dynamically when tags might get dirty or damaged

313
00:15:12.120 --> 00:15:15.519
<v Speaker 2>around metal, though UHF often handles metal better than HF

314
00:15:16.039 --> 00:15:19.320
<v Speaker 2>for longer read ranges and especially for reading many items

315
00:15:19.320 --> 00:15:21.919
<v Speaker 2>at once, like a whole palette load passing through a gate.

316
00:15:22.159 --> 00:15:26.200
<v Speaker 2>And two D codes, there's strong contenders for simpler applications,

317
00:15:26.440 --> 00:15:30.120
<v Speaker 2>especially where you can ensure good contrast when direct marking

318
00:15:30.159 --> 00:15:32.440
<v Speaker 2>is the best option and when a human might need

319
00:15:32.480 --> 00:15:34.279
<v Speaker 2>to visually verify the code.

320
00:15:33.960 --> 00:15:37.519
<v Speaker 1>And for production control, integration is key for both.

321
00:15:37.360 --> 00:15:41.799
<v Speaker 2>Absolutely connecting two industrial networks plc's production planning systems. That's

322
00:15:41.840 --> 00:15:44.879
<v Speaker 2>critical regardless of whether you choose RFID or two D codes,

323
00:15:45.440 --> 00:15:49.200
<v Speaker 2>though rfid's longer range does enable things like tracking forklifts,

324
00:15:49.279 --> 00:15:51.919
<v Speaker 2>driving through doorways, which is harder with optical codes.

325
00:15:52.000 --> 00:15:56.159
<v Speaker 1>Okay, the outline mentions closed loop r FID. What's that about?

326
00:15:56.320 --> 00:15:57.080
<v Speaker 3>Right? Closed loop?

327
00:15:57.200 --> 00:16:00.519
<v Speaker 2>These systems have been used for years, mainly in making complex,

328
00:16:00.720 --> 00:16:03.519
<v Speaker 2>configurable products. Cars are a classic example.

329
00:16:03.559 --> 00:16:04.039
<v Speaker 1>How does it work?

330
00:16:04.240 --> 00:16:07.159
<v Speaker 2>An RFID tag is put on a reusable carrier that

331
00:16:07.279 --> 00:16:10.759
<v Speaker 2>follows the product through assembling and testing. The tag holds

332
00:16:10.840 --> 00:16:15.120
<v Speaker 2>data that guides each step. Crucially, after one product is finished,

333
00:16:15.480 --> 00:16:19.279
<v Speaker 2>the tag isn't thrown away, It's reused. It's data updated

334
00:16:19.519 --> 00:16:21.240
<v Speaker 2>for the next product going down the line.

335
00:16:21.360 --> 00:16:24.039
<v Speaker 1>Ah, So the tag stays within the factory system.

336
00:16:23.919 --> 00:16:27.399
<v Speaker 2>Exactly, and because it's reused one hundreds or thousands of times,

337
00:16:27.840 --> 00:16:30.919
<v Speaker 2>the actual cost of that individual tag becomes less of

338
00:16:30.960 --> 00:16:33.399
<v Speaker 2>a big deal compared to the value that data carries

339
00:16:33.399 --> 00:16:34.960
<v Speaker 2>and enables got it.

340
00:16:35.000 --> 00:16:38.320
<v Speaker 1>Focus shifts to reusability and the data. Now standardization You

341
00:16:38.360 --> 00:16:41.960
<v Speaker 1>mentioned it earlier, but why is it so fundamentally important.

342
00:16:42.080 --> 00:16:46.000
<v Speaker 2>It's absolutely critical for interoperability, especially in open supply chains,

343
00:16:46.000 --> 00:16:46.840
<v Speaker 2>where goods move.

344
00:16:46.720 --> 00:16:48.279
<v Speaker 3>Between different companies different partners.

345
00:16:48.519 --> 00:16:51.240
<v Speaker 2>Without standards, you risk having a reader from company A

346
00:16:51.879 --> 00:16:54.039
<v Speaker 2>not being able to read a tag from company.

347
00:16:53.679 --> 00:16:54.960
<v Speaker 1>B, create silos.

348
00:16:55.000 --> 00:16:59.279
<v Speaker 2>Basically, precisely, standardization ensures data flows smoothly across the whole chain.

349
00:17:00.039 --> 00:17:02.519
<v Speaker 2>Can lead to more competitive pricing because more vendors can

350
00:17:02.519 --> 00:17:05.799
<v Speaker 2>make compatible gear. It focuses R and D efforts, and

351
00:17:05.839 --> 00:17:08.079
<v Speaker 2>it gives the industry a stronger voice when talking to

352
00:17:08.160 --> 00:17:11.519
<v Speaker 2>regulators about things like frequency use. If you're just using

353
00:17:11.640 --> 00:17:15.000
<v Speaker 2>RFID inside your own four walls with tags you control

354
00:17:15.000 --> 00:17:18.559
<v Speaker 2>and reuse, maybe less critical, but for tracking goods across

355
00:17:18.599 --> 00:17:19.519
<v Speaker 2>companies it's essential.

356
00:17:19.839 --> 00:17:22.440
<v Speaker 1>So what are the key standards we should know about.

357
00:17:22.599 --> 00:17:25.319
<v Speaker 2>It's been a bit complex getting here, with different frequencies

358
00:17:25.319 --> 00:17:28.559
<v Speaker 2>in all but a major one is ISEC eighteen thousand,

359
00:17:29.160 --> 00:17:32.960
<v Speaker 2>that defines the air interface the wireless link for identifying goods.

360
00:17:32.880 --> 00:17:34.240
<v Speaker 1>And that covers all frequencies.

361
00:17:34.279 --> 00:17:36.799
<v Speaker 2>It's actually a series of standards. Different parts cover lf

362
00:17:37.079 --> 00:17:39.920
<v Speaker 2>HF UAHF even two point four five gearer it's and

363
00:17:39.960 --> 00:17:42.240
<v Speaker 2>four hundred and thirty three mili herds. Because the physics

364
00:17:42.240 --> 00:17:44.359
<v Speaker 2>is different at each frequency, you need different protocols.

365
00:17:44.400 --> 00:17:46.759
<v Speaker 1>Okay, ISO eighteen thousand for the air interface.

366
00:17:47.119 --> 00:17:50.160
<v Speaker 2>Others, yeah, other isostandards covered data protocols, how data is

367
00:17:50.160 --> 00:17:53.160
<v Speaker 2>structured unique ID schemes like one with nine six one

368
00:17:53.200 --> 00:17:55.759
<v Speaker 2>one foot nine six two one five nine six three.

369
00:17:55.799 --> 00:17:58.559
<v Speaker 2>There are also applications specific standards, and you can't forget

370
00:17:58.559 --> 00:18:01.039
<v Speaker 2>GS one. The Barcode people, they are huge in RFID

371
00:18:01.119 --> 00:18:02.200
<v Speaker 2>too with their EPC.

372
00:18:01.960 --> 00:18:05.279
<v Speaker 1>Global Standards EPC Electronic Product Code right.

373
00:18:05.599 --> 00:18:08.319
<v Speaker 2>And then there are the telecommunications regulations in each country

374
00:18:08.640 --> 00:18:13.240
<v Speaker 2>managing frequency use to avoid interference with TV, radio, mobile phones.

375
00:18:12.880 --> 00:18:13.359
<v Speaker 3>Et cetera.

376
00:18:13.599 --> 00:18:17.440
<v Speaker 1>So a whole ecosystem of standards and regulations. Now, imagine

377
00:18:17.519 --> 00:18:19.799
<v Speaker 1>a company is ready to take the plunge they want

378
00:18:19.839 --> 00:18:24.400
<v Speaker 1>to implement RFID. What's the process look like designing and

379
00:18:24.440 --> 00:18:25.359
<v Speaker 1>deploying it.

380
00:18:25.359 --> 00:18:28.079
<v Speaker 2>It usually starts with a really thorough planning phase. You

381
00:18:28.160 --> 00:18:30.799
<v Speaker 2>need to analyze the current situation, how things work now,

382
00:18:31.200 --> 00:18:33.279
<v Speaker 2>to find a clear vision what do we want to

383
00:18:33.319 --> 00:18:38.119
<v Speaker 2>achieve with RFID? Set specific goals for performance business processes.

384
00:18:38.200 --> 00:18:39.559
<v Speaker 1>So strategy first.

385
00:18:39.759 --> 00:18:44.359
<v Speaker 2>Absolutely understand the impacts across the organization. Prioritize where to start.

386
00:18:44.559 --> 00:18:48.319
<v Speaker 2>Ask those big questions, is our current model competitive long term?

387
00:18:48.440 --> 00:18:50.680
<v Speaker 2>What do customers want next? What tech do we need

388
00:18:50.720 --> 00:18:53.880
<v Speaker 2>for the future? Where can we find efficiencies or boost profits?

389
00:18:54.000 --> 00:18:56.039
<v Speaker 1>A deep internal look then what?

390
00:18:56.359 --> 00:18:59.079
<v Speaker 2>Then you get into the details. Map out the specific

391
00:18:59.119 --> 00:19:03.279
<v Speaker 2>processes you want to improve. Model their performance, time, cost quality.

392
00:19:03.519 --> 00:19:05.559
<v Speaker 2>Compare the as is state with the two B state

393
00:19:05.759 --> 00:19:08.319
<v Speaker 2>using best practices or ideas enabled by RFID.

394
00:19:08.480 --> 00:19:10.160
<v Speaker 1>The gap analysis exactly.

395
00:19:10.839 --> 00:19:15.400
<v Speaker 2>That leads to designing the new RFAD enabled process, and critically,

396
00:19:15.440 --> 00:19:17.599
<v Speaker 2>you need a solid business case.

397
00:19:17.720 --> 00:19:18.359
<v Speaker 1>The money part.

398
00:19:19.039 --> 00:19:23.440
<v Speaker 2>Compare all the costs hardware, software, consulting, implementation, ongoing operations

399
00:19:23.759 --> 00:19:28.160
<v Speaker 2>against all the expected benefits productivity games, higher turnover from

400
00:19:28.160 --> 00:19:32.400
<v Speaker 2>better inventory, cost savings. You can use simple ROI calculations

401
00:19:32.480 --> 00:19:34.200
<v Speaker 2>or more complex dynamic models.

402
00:19:34.000 --> 00:19:36.119
<v Speaker 1>And before rolling it out everywhere.

403
00:19:35.680 --> 00:19:39.440
<v Speaker 2>Testing feasibility tests, pilot projects in realistic settings.

404
00:19:39.720 --> 00:19:40.440
<v Speaker 3>This is crucial.

405
00:19:40.920 --> 00:19:43.839
<v Speaker 2>Verify the tech works reliably in your environment, refine the

406
00:19:43.880 --> 00:19:47.640
<v Speaker 2>cost benefit numbers, Ensure it integrates smoothly with existing systems,

407
00:19:48.039 --> 00:19:51.720
<v Speaker 2>check data synchronization, find those unexpected challenges like maybe you

408
00:19:51.759 --> 00:19:54.000
<v Speaker 2>can't quote hit one hundred percent read rates because of

409
00:19:54.000 --> 00:19:55.400
<v Speaker 2>metal interference in one area.

410
00:19:55.559 --> 00:19:57.519
<v Speaker 1>So iron out the kinks before going big.

411
00:19:57.599 --> 00:20:01.480
<v Speaker 2>Precisely, Pilots test accuracy, data flow, low performance under real load.

412
00:20:01.559 --> 00:20:03.279
<v Speaker 3>It's where you troubleshoot and learn.

413
00:20:03.400 --> 00:20:06.240
<v Speaker 1>Makes sense. A phased, careful approach. Let's shift to some

414
00:20:06.279 --> 00:20:10.680
<v Speaker 1>real world applications. Now, mass customization making individualized products efficiently.

415
00:20:10.759 --> 00:20:12.079
<v Speaker 1>How does RFID help there?

416
00:20:12.319 --> 00:20:15.960
<v Speaker 2>Mass customization is driven by customer demand and global competition.

417
00:20:16.640 --> 00:20:21.119
<v Speaker 2>It requires super flexible manufacturing and supply chains. RFID is

418
00:20:21.160 --> 00:20:24.359
<v Speaker 2>a key enabler. Any example, Siemens Amberg plant in Germany

419
00:20:24.440 --> 00:20:27.559
<v Speaker 2>is a great one. They make serious switching devices thousands

420
00:20:27.599 --> 00:20:30.440
<v Speaker 2>of variations. They guarantee twenty four hour delivery.

421
00:20:30.599 --> 00:20:31.759
<v Speaker 1>Howafid yep.

422
00:20:31.839 --> 00:20:34.440
<v Speaker 2>Each device is built on a workpiece carrier with an

423
00:20:34.559 --> 00:20:38.559
<v Speaker 2>RFID chip. That chip holds all the specific instructions and

424
00:20:38.640 --> 00:20:41.759
<v Speaker 2>parts list for that exact version. As it moves down

425
00:20:41.799 --> 00:20:44.960
<v Speaker 2>the automated line, each station reads the chip and knows

426
00:20:45.000 --> 00:20:47.200
<v Speaker 2>precisely what to do for that specific unit.

427
00:20:47.359 --> 00:20:49.680
<v Speaker 1>Wow, So the product itself tells the machines how to

428
00:20:49.680 --> 00:20:50.039
<v Speaker 1>build it.

429
00:20:50.079 --> 00:20:50.559
<v Speaker 3>Pretty much.

430
00:20:50.599 --> 00:20:53.400
<v Speaker 2>It allows incredible flexibility just in time production for a

431
00:20:53.480 --> 00:20:54.359
<v Speaker 2>huge product mix.

432
00:20:54.440 --> 00:20:58.559
<v Speaker 1>That's a powerful example. What about general production logistics moving

433
00:20:58.599 --> 00:21:00.759
<v Speaker 1>materials around.

434
00:20:59.759 --> 00:21:04.240
<v Speaker 2>The roles There are usually low inventory, fast throughput, flexibility, quality,

435
00:21:04.599 --> 00:21:09.200
<v Speaker 2>all while handling more product variants. RFID impacts incoming outgoing goods,

436
00:21:09.720 --> 00:21:12.559
<v Speaker 2>transport handling, picking, storage.

437
00:21:12.079 --> 00:21:13.200
<v Speaker 1>And inventory management.

438
00:21:13.400 --> 00:21:17.519
<v Speaker 2>It enables things like vendor managed inventory VMI. The source

439
00:21:17.559 --> 00:21:21.759
<v Speaker 2>mentions FINSA, a Spanish panel manufacturer. They use RFID tags

440
00:21:21.799 --> 00:21:24.759
<v Speaker 2>on big bags of resin from their supplier.

441
00:21:24.359 --> 00:21:26.720
<v Speaker 1>DSM, tracking raw materials exactly.

442
00:21:27.319 --> 00:21:30.359
<v Speaker 2>Unique EPC tags let them automate tracking through storage and

443
00:21:30.440 --> 00:21:35.000
<v Speaker 2>monitor usage in real time across multiple plants. Result better

444
00:21:35.000 --> 00:21:38.400
<v Speaker 2>storage use, fewer errors, lower logistics costs.

445
00:21:38.119 --> 00:21:41.640
<v Speaker 1>So visibility from the supplier right into production. What about

446
00:21:41.640 --> 00:21:44.279
<v Speaker 1>reusable things like palettes and containers RTIs?

447
00:21:44.400 --> 00:21:48.039
<v Speaker 2>Yeah, reusable transport items crucial for B to B supply chains.

448
00:21:48.279 --> 00:21:52.319
<v Speaker 2>To track these effectively between suppliers, customers, logistics providers, each

449
00:21:52.440 --> 00:21:56.640
<v Speaker 2>RTI needs a unique ID. Standards like GRAI Global Returnable

450
00:21:56.640 --> 00:21:58.000
<v Speaker 2>Asset Identifier.

451
00:21:57.519 --> 00:21:59.839
<v Speaker 1>Are used and RFID provides the tracking.

452
00:22:00.000 --> 00:22:02.759
<v Speaker 2>It provides a transparency. You can manage inventory of containers,

453
00:22:02.799 --> 00:22:05.920
<v Speaker 2>track their location, even monitor their condition important if they

454
00:22:05.920 --> 00:22:09.000
<v Speaker 2>need maintenance. There are even business models built around selling

455
00:22:09.000 --> 00:22:12.759
<v Speaker 2>and repurchasing containers, and RFID helps track ownership and costs

456
00:22:12.759 --> 00:22:13.200
<v Speaker 2>there too.

457
00:22:13.519 --> 00:22:16.839
<v Speaker 1>Tracking the container not just the contents makes sense. What

458
00:22:16.880 --> 00:22:18.759
<v Speaker 1>about tracking and tracing for visibility and.

459
00:22:18.799 --> 00:22:22.240
<v Speaker 2>Quality essential for things like just in time or just

460
00:22:22.319 --> 00:22:26.319
<v Speaker 2>in sequence logistics, You need real time info on shipment

461
00:22:26.359 --> 00:22:27.480
<v Speaker 2>location and status.

462
00:22:27.559 --> 00:22:28.440
<v Speaker 1>What are the benefits?

463
00:22:28.599 --> 00:22:33.960
<v Speaker 2>Huge advantages optimizing manufacturing, reacting quickly to disruptions, giving customers

464
00:22:33.960 --> 00:22:38.000
<v Speaker 2>more accurate delivery info. Plus legal requirements are pushing this thing.

465
00:22:38.079 --> 00:22:42.799
<v Speaker 2>Pharmaceuticals and FDA rules and consumers demand more transparency.

466
00:22:42.079 --> 00:22:43.839
<v Speaker 1>Too, and quality assurance.

467
00:22:44.200 --> 00:22:49.519
<v Speaker 2>RFID enables proactive QA direct access to info about products, equipment.

468
00:22:49.759 --> 00:22:52.400
<v Speaker 2>Has this item stayed within its temperature range? Has this

469
00:22:52.440 --> 00:22:56.680
<v Speaker 2>tool been maintained? You can catch problems before they cause defects.

470
00:22:56.240 --> 00:23:00.000
<v Speaker 1>Preventing issues, not just reacting. How does RFID help company

471
00:23:00.279 --> 00:23:04.279
<v Speaker 1>keep up with evolving business demands? Generally more products, complex

472
00:23:04.319 --> 00:23:05.440
<v Speaker 1>supply chains.

473
00:23:05.200 --> 00:23:08.880
<v Speaker 2>Right, product variety is exploding, Supply networks are global and complex,

474
00:23:09.000 --> 00:23:13.559
<v Speaker 2>competition is fierce. Companies need technologies like RFID for efficiency.

475
00:23:14.079 --> 00:23:17.519
<v Speaker 2>While factories are often automated internally, that cross company link

476
00:23:17.599 --> 00:23:21.640
<v Speaker 2>often lacks item level automation, lots of manual work poor visibility.

477
00:23:21.880 --> 00:23:25.119
<v Speaker 1>RFID can fix that, bridging the gaps between companies.

478
00:23:24.640 --> 00:23:28.160
<v Speaker 2>Exactly, and it helps after the sale too, streamlining warranty claims,

479
00:23:28.480 --> 00:23:29.839
<v Speaker 2>managing loan equipment better.

480
00:23:29.880 --> 00:23:34.799
<v Speaker 1>Okay, let's talk about real time locating systems RTLS using RFID.

481
00:23:35.200 --> 00:23:36.000
<v Speaker 1>How do they work?

482
00:23:36.240 --> 00:23:39.799
<v Speaker 2>These are usually active RFID systems. The tags have batteries

483
00:23:39.960 --> 00:23:43.599
<v Speaker 2>and actively broadcast signals periodically like little beacons, sort of

484
00:23:43.920 --> 00:23:47.920
<v Speaker 2>a network of fixed receivers. RTLS access points picks up

485
00:23:47.920 --> 00:23:51.880
<v Speaker 2>these signals by analyzing signal strength, time of arrival angle.

486
00:23:52.240 --> 00:23:55.279
<v Speaker 2>A central system calculates the tag's location in real.

487
00:23:55.079 --> 00:23:58.319
<v Speaker 1>Time pinpoint location and not just presence. Where is this used?

488
00:23:58.839 --> 00:24:01.720
<v Speaker 2>Vehicle logistics in car our plants is one example, tracking

489
00:24:01.759 --> 00:24:05.839
<v Speaker 2>cars through assembly, reducing search time, Fleet management for public transport,

490
00:24:05.920 --> 00:24:09.720
<v Speaker 2>optimizing schedules, maintenance, fuel, and even security and logistics on

491
00:24:09.839 --> 00:24:14.200
<v Speaker 2>large factory sites. Electronic access authorization for trucks based on

492
00:24:14.200 --> 00:24:15.400
<v Speaker 2>their RFID tags.

493
00:24:15.559 --> 00:24:18.559
<v Speaker 1>Precise location tracking opens up a lot of possibilities. What

494
00:24:18.599 --> 00:24:20.319
<v Speaker 1>about specific industries? Airports?

495
00:24:20.480 --> 00:24:24.759
<v Speaker 2>Airports are adopting RSID significantly, especially for baggage handling. IAD

496
00:24:24.880 --> 00:24:27.599
<v Speaker 2>even has recommendations for UHF tags on bag.

497
00:24:27.359 --> 00:24:29.119
<v Speaker 1>Tags to reduce lost luggage.

498
00:24:29.200 --> 00:24:32.440
<v Speaker 2>That's a major goal. Better tracking through the conveyor system

499
00:24:32.519 --> 00:24:36.480
<v Speaker 2>means fewer mishandled bags, more efficiency. But it's also used

500
00:24:36.480 --> 00:24:40.319
<v Speaker 2>for catering trolleys, freight vehicles on the airside, tracking maintenance

501
00:24:40.400 --> 00:24:44.279
<v Speaker 2>on valuable aircraft parts, reconciling bags with passengers, even cargo

502
00:24:44.559 --> 00:24:48.039
<v Speaker 2>YEP tagging you'ld's unit load devices for precise tracking of

503
00:24:48.039 --> 00:24:48.559
<v Speaker 2>air freight.

504
00:24:48.880 --> 00:24:51.880
<v Speaker 1>Okay, Airports are a big one. Postal services are they

505
00:24:51.960 --> 00:24:52.680
<v Speaker 1>using it much?

506
00:24:52.960 --> 00:24:56.400
<v Speaker 2>Barcodes are still dominant for individual mail items there, but

507
00:24:56.599 --> 00:25:00.920
<v Speaker 2>RFID is growing for reusable assets, containers, transport.

508
00:25:00.559 --> 00:25:03.880
<v Speaker 1>Vehicles, the closed loop idea again exactly cost effective.

509
00:25:03.960 --> 00:25:08.319
<v Speaker 2>UAHF passive tags, smart labels work well on plastic mail tubs,

510
00:25:08.559 --> 00:25:12.400
<v Speaker 2>active tags for longer ranges. Rtls can track container locations

511
00:25:12.440 --> 00:25:13.279
<v Speaker 2>across the network.

512
00:25:13.400 --> 00:25:15.000
<v Speaker 1>Not on every letter yet not really.

513
00:25:15.079 --> 00:25:17.240
<v Speaker 2>Cost is still a factor, but they are using it

514
00:25:17.279 --> 00:25:20.759
<v Speaker 2>for quality control, putting RFID tags on test letters to

515
00:25:20.799 --> 00:25:22.880
<v Speaker 2>track transit times and find bottlenecks.

516
00:25:23.039 --> 00:25:25.920
<v Speaker 1>Clever use case all right, healthcare, this seems like a

517
00:25:25.960 --> 00:25:28.680
<v Speaker 1>domain with huge potential impact for RFID.

518
00:25:29.000 --> 00:25:33.640
<v Speaker 2>Absolutely, patient safety is paramount. RFID helps tackle critical issues

519
00:25:33.720 --> 00:25:38.759
<v Speaker 2>like patient misidentification, medication errors, things that can have terrible consequences.

520
00:25:38.839 --> 00:25:42.759
<v Speaker 2>How risk bands, Yes, RFID wristbands like a clinicum Sarbruken

521
00:25:43.200 --> 00:25:46.319
<v Speaker 2>or patient ID cards like medical art uses. Doctors and

522
00:25:46.400 --> 00:25:50.079
<v Speaker 2>nurses use mobile readers to instantly verify identity and access

523
00:25:50.160 --> 00:25:52.240
<v Speaker 2>vital infoologies.

524
00:25:51.720 --> 00:25:54.119
<v Speaker 1>History faster, more accurate, right.

525
00:25:54.200 --> 00:25:58.240
<v Speaker 2>Improves data accuracy, reduces paperwork freeze up time for actual

526
00:25:58.319 --> 00:26:02.799
<v Speaker 2>patient care. Security is obviously vital, so encryption protects patient privacy.

527
00:26:03.359 --> 00:26:06.839
<v Speaker 2>Some systems even let patients access their own info via terminals.

528
00:26:06.880 --> 00:26:10.640
<v Speaker 2>What else in hospitals tracking reusable surgical equipment, managing cleaning cycles,

529
00:26:10.720 --> 00:26:14.559
<v Speaker 2>inventory tracking staff presents and roles, in operating rooms using badges,

530
00:26:14.799 --> 00:26:18.839
<v Speaker 2>providing data on operation phases without storing personal details. And

531
00:26:18.880 --> 00:26:21.960
<v Speaker 2>in maternity wards using RFID for newborn ID to prevent

532
00:26:22.000 --> 00:26:24.279
<v Speaker 2>mix ups. That's a huge relief for parents.

533
00:26:24.519 --> 00:26:27.799
<v Speaker 1>Definitely addresses some major safety concerns. Looking ahead, now, what's

534
00:26:27.839 --> 00:26:31.440
<v Speaker 1>next for RFID Printed electronics item level tagging?

535
00:26:31.680 --> 00:26:32.799
<v Speaker 3>The future looks bright.

536
00:26:33.559 --> 00:26:37.480
<v Speaker 2>Printed electronics, like the work POLYLC is doing, promises really

537
00:26:37.519 --> 00:26:42.720
<v Speaker 2>low cost, thin, flexible tags made using role to role processes.

538
00:26:42.240 --> 00:26:44.119
<v Speaker 1>Making tags almost like printing labels.

539
00:26:44.240 --> 00:26:49.160
<v Speaker 2>Kind Of yeah, this could dramatically expand applications, fighting counterfeit drugs,

540
00:26:49.359 --> 00:26:53.559
<v Speaker 2>ensuring food trace stability, brand protection with intelligent seals. The

541
00:26:53.599 --> 00:26:56.400
<v Speaker 2>big dream for many is item level tagging.

542
00:26:56.680 --> 00:26:58.720
<v Speaker 1>Tagging every single item.

543
00:26:58.599 --> 00:27:02.880
<v Speaker 2>Pretty much product gets a unique electronic product code EPC

544
00:27:03.400 --> 00:27:07.559
<v Speaker 2>that allows near perfect authentication, full traceability from factory to consumer.

545
00:27:07.720 --> 00:27:12.559
<v Speaker 1>A massive undertaking, but potentially transformative. What about combining RFID with.

546
00:27:12.640 --> 00:27:16.400
<v Speaker 2>Sensors another huge area. Integrating sensors with the RFID tag

547
00:27:16.480 --> 00:27:22.319
<v Speaker 2>so you're not just tracking location, but also environmental conditions temperature, humidity, pressure, shock, vibration.

548
00:27:22.400 --> 00:27:23.240
<v Speaker 1>Why is that useful?

549
00:27:23.400 --> 00:27:27.359
<v Speaker 2>Think temperature sensitive goods, blood supplies, pharmaceuticals, even wine. You

550
00:27:27.359 --> 00:27:30.759
<v Speaker 2>can monitor their condition throughout the supply chain, insure quality,

551
00:27:30.880 --> 00:27:34.200
<v Speaker 2>know who's responsible if something goes wrong, same for humidity

552
00:27:34.240 --> 00:27:35.920
<v Speaker 2>sensitive items in shipping containers.

553
00:27:36.160 --> 00:27:40.319
<v Speaker 1>Adding environmental context to the tracking data very powerful. But

554
00:27:40.440 --> 00:27:44.440
<v Speaker 1>with all this tracking, security and privacy concerns must be significant.

555
00:27:44.480 --> 00:27:47.720
<v Speaker 2>They absolutely are reading tags at point of sale, for instance,

556
00:27:47.960 --> 00:27:50.599
<v Speaker 2>raises privacy flags about building personal profiles.

557
00:27:50.920 --> 00:27:52.200
<v Speaker 1>How is the data secured?

558
00:27:52.680 --> 00:27:55.400
<v Speaker 2>Symmetrical encryption is one way, but you have to protect

559
00:27:55.400 --> 00:27:59.200
<v Speaker 2>the shared secret key. If that key gets compromised, security

560
00:27:59.240 --> 00:28:04.279
<v Speaker 2>is gone, key length algorithm strength are crucial. Storing keys

561
00:28:04.319 --> 00:28:07.200
<v Speaker 2>in readers is also a risk if the reader is stolen.

562
00:28:06.960 --> 00:28:09.359
<v Speaker 1>Or hacked, and cloning tags.

563
00:28:09.079 --> 00:28:12.279
<v Speaker 2>Is that a threat a major one, especially for valuable

564
00:28:12.319 --> 00:28:15.720
<v Speaker 2>items or access control eavesdropping on the communication and then

565
00:28:15.720 --> 00:28:16.519
<v Speaker 2>making a copy.

566
00:28:16.799 --> 00:28:18.599
<v Speaker 1>Are there better security approaches?

567
00:28:18.799 --> 00:28:23.519
<v Speaker 2>Asymmetrical encryption public private keys is generally stronger. Data encrypted

568
00:28:23.559 --> 00:28:25.720
<v Speaker 2>with the public key can only be decrypted by the

569
00:28:25.720 --> 00:28:31.720
<v Speaker 2>private keyholder. Digital signatures add authenticity. PKI public key infrastructure

570
00:28:31.920 --> 00:28:33.880
<v Speaker 2>adds another layer with trusted authorities.

571
00:28:34.039 --> 00:28:36.200
<v Speaker 1>Can passive tags handle that kind of crypto?

572
00:28:36.359 --> 00:28:39.880
<v Speaker 2>It's challenging. They typically lack the computing power for standard

573
00:28:39.880 --> 00:28:43.799
<v Speaker 2>PKI right now, but research is ongoing whether we'll see

574
00:28:43.839 --> 00:28:47.759
<v Speaker 2>strong security as a default feature. Well, cost pressures and

575
00:28:47.880 --> 00:28:51.160
<v Speaker 2>varying needs across applications make that uncertain.

576
00:28:50.880 --> 00:28:55.160
<v Speaker 1>A constant trade off between cost, convenience and security. Finally,

577
00:28:55.200 --> 00:28:57.279
<v Speaker 1>let's zoom out. How does all this fit into the

578
00:28:57.319 --> 00:28:59.279
<v Speaker 1>bigger picture? The Internet of Things?

579
00:29:00.039 --> 00:29:03.680
<v Speaker 2>True supply teain management needs coordination across all value adding steps.

580
00:29:04.000 --> 00:29:09.160
<v Speaker 2>Tightly integrated logistics globalization e commerce. They made logistics networks

581
00:29:09.160 --> 00:29:10.920
<v Speaker 2>incredibly complex and dynamic.

582
00:29:11.079 --> 00:29:12.480
<v Speaker 1>It integration is key.

583
00:29:12.720 --> 00:29:16.960
<v Speaker 2>Essentral connecting suppliers, service providers, customers to prevent errors, manage

584
00:29:17.000 --> 00:29:21.279
<v Speaker 2>the complexity. Autoid bar codes RFID are the eyes and

585
00:29:21.319 --> 00:29:22.799
<v Speaker 2>ears identifying things.

586
00:29:22.640 --> 00:29:24.400
<v Speaker 1>In these networks, and the IoT vision.

587
00:29:24.519 --> 00:29:30.000
<v Speaker 2>It envisions more decentralized intelligence, objects themselves having some processing power, sensors, connectivity.

588
00:29:30.200 --> 00:29:33.240
<v Speaker 2>Think of that baggage system again. Maybe components making local

589
00:29:33.279 --> 00:29:36.880
<v Speaker 2>decisions instead of one central brain controlling everything. More autonomous,

590
00:29:37.039 --> 00:29:38.680
<v Speaker 2>potentially more resilient and efficient.

591
00:29:38.920 --> 00:29:41.440
<v Speaker 1>Okay, let's wrap up with some key takeaways from this

592
00:29:41.519 --> 00:29:42.000
<v Speaker 1>deep dive.

593
00:29:42.319 --> 00:29:44.920
<v Speaker 2>We've really journeyed through the world of r FID and

594
00:29:45.000 --> 00:29:50.559
<v Speaker 2>autoid from their somewhat humble beginnings to their vital role

595
00:29:50.599 --> 00:29:53.279
<v Speaker 2>today and the exciting future. You should now have a

596
00:29:53.279 --> 00:29:56.240
<v Speaker 2>good grasp of what they are, how they work, where

597
00:29:56.279 --> 00:29:59.119
<v Speaker 2>they're used, the challenges, and how they're evolving.

598
00:29:59.279 --> 00:30:03.000
<v Speaker 1>And don't forget that's surprising fact. The first industrial RFID

599
00:30:03.119 --> 00:30:06.839
<v Speaker 1>system MOBM had that tiny red range shorter than your thumb,

600
00:30:06.960 --> 00:30:08.000
<v Speaker 1>but it taved.

601
00:30:07.720 --> 00:30:11.160
<v Speaker 2>The way absolutely and the relevance for you the listener,

602
00:30:11.359 --> 00:30:14.799
<v Speaker 2>whether you're in business, tech or just curious. Understanding these

603
00:30:14.799 --> 00:30:18.359
<v Speaker 2>technologies gives context to the automated systems shaping our world.

604
00:30:18.680 --> 00:30:23.680
<v Speaker 2>Seeingless logistics, safer healthcare. They're quietly revolutionizing processes we often

605
00:30:23.720 --> 00:30:24.480
<v Speaker 2>take for granted.

606
00:30:24.799 --> 00:30:28.079
<v Speaker 1>Okay, one final provocative thought to leave you with as

607
00:30:28.119 --> 00:30:31.720
<v Speaker 1>we move deeper into this interconnected Internet of things, What

608
00:30:31.880 --> 00:30:36.039
<v Speaker 1>unforeseen applications, what societal impacts good or bad might emerge

609
00:30:36.039 --> 00:30:38.599
<v Speaker 1>from being able to track and identify almost anything.

610
00:30:39.039 --> 00:30:42.559
<v Speaker 2>That's definitely something worth pondering as this technological landscape keeps

611
00:30:42.640 --> 00:30:43.079
<v Speaker 2>unfolding