シャドーイング練習: Traceability 101: An Introduction to Food Supply Chain Traceability - 動画で英語スピーキングを学ぶ

Thank you, Mark.

We truly appreciate the opportunity to join you

and the entire AFTO community today to talk about a topic near and dear to our heart and to all of us.

So Thomas and I are going to tag team today if we then move to the next slide.

So first of all, we wanted to give you a sense of the scope of the topic

that we'd like to talk to.

First of all, we're going to give a little bit more background on Thomas and IA's role.

We're going to talk about concepts, standards, where digital technology is today, spend quite a bit of time on interoperability, which is a key concept

that we want to make all of you have a deep understanding on and what that means to the end-to-end supply chain.

We also want to talk a little bit more about how this looks like in the future, specifically for your roles in your day-to-day life.

And then we'll wrap up, hopefully, with 10 to 15 minutes of Q&A.

so you can ask us any questions

that you have on the top of your mind that's what

we'd like to cover today I know we have a short one-hour timeframe

but we'll try to get through as much as we can

and give you a nice solid grounding or traceability conversation is today

so next is you know webinars are always great to be able to put a name

and a face together so there you see a picture myself.

I come to the ISP about a year ago after a

20-plus year career in the food CPG industry across Procter & Gamble

and PepsiCo in various different roles of product process quality development type of roles commercializing new products

and new technologies to the marketplace.

Thomas how about you go ahead and introduce a little bit more about yourself.

Thanks Brian.

So here's my head shot so you have an idea of what I look like.

I do wish I had taken my gotten a haircut before I took this picture but there's me.

I have a background in microbiology and epidemiology and currently pursuing further education in food science.

I kind of found this niche in food traceability research and early implementation and standardization.

I was involved in trace back investigations

while at the Georgia Department of Agriculture in their food safety division

and I really saw a need for improving end-to-end traceability capabilities

and I've at the moment now I lead interoperability work for the global dialogue CPU traceability

which I'll kind of go into a little bit more detail how

that applies more broadly to enabling better traceability systems but yeah

so they're three file on me and I'm gonna head back off to Brian

so you can start us off here sure

so we thought we gave a little bit of background on IFT

and how that fits into the traceability space

so first of all a little bit about ifd so ift is a 15 000 member individual member community

focused on the science of food delivering safe nutritious

and sustainable food supplies to the world ift

and traceability specifically has a you know 12-year history going back to partnerships between ift

and the fda in preparation for the creation

and rollout of fisma as you can see on the slide

here multiple year engagements with contract work with the FDA convening

experts across multiple stakeholder groups to conduct pilot traceback investigations and identifying some recommendations that ultimately were put into section 204 regulation.

After we did that work, we transitioned somewhat into a partnership working specifically in the seafood traceability space.

We chose seafood for multiple reasons that we'll get to in a little bit deeper into the later in the presentation.

But the complexity, global scale, and the use cases

that were of need there really sought us to choose seafood as a commodity of interest

that we would put our focus on.

Speaking of use cases, on the next slide, we'll try to summarize this in a couple different ways.

Many of us think of traceability as focused on recall management and the food safety aspects of that.

But ultimately, traceability systems and the backbone of information that they create have a lot of different use cases,

including sustainability, fighting fraud, legality, provenance, and chain of custody.

We believe that all of this ladders up to higher order consumer needs, such as trust and transparency, and having confidence in their food supply that they're getting the

purchase and it's safe for them

and their families to use just want to ground a little

bit of you know everyone in the case of where we're traceability data can be used now

that we're going to go in a little bit deeper into concepts

and other areas I'll let you hand it off to Thomas

to take you into the next layer of depth Thomas take it away thanks Brian

so we're gonna first start talking traceability concepts I kind of

want to preface this discussion with this is how we have seen traceability evolved

and how businesses currently think about traceability

when they're thinking about enabling better trace back mechanisms

and also addressing those use cases that Brian had talked about there's been

because of the spark and you know possibilities and digital technology

There's been all sorts of use cases that have been played with

and have been having early implementation that go beyond food safety.

So I want to kind of center some of the concepts on what our business is thinking about

when they're thinking about traceability and how that applies to traceback investigations

and what you may be using in your familiarity with traceability.

So here's kind of what the current paradigm is, is one up, one down traceability.

It comes out of the 2002 Antibiotera Act where we needed to have a record keeping requirement

so that there can be the ability to easily trace back

or to facilitate trace back investigation in the event of a food emergency.

So this is kind of displaying the kind of what the scenario is practically from a systems design point of view.

So because you have basically the record keeping components of that you're keeping the records on your customers and on your suppliers,

you end up having unique critical junctures where that you that are you have special relationships between them.

You may have actually a different way of keeping that information depending on what your relationship is.

So you end up having all of these types of relationships that you're managing just on the single supply chain node.

This kind of works for internal traceability purposes, but when you are needing to connect the dots across the supply chain,

especially if you need to have origin data, you have

quite a bit of problems because you're actually having to connect this situation multiple times

and in food supply chains that you can actually have quite a few different nodes you can have

fragmented supply chains you can have very different ways of keeping this information

and the way you keep the information especially from paper records

maybe it's been on a particular person knowing where it is

so it's it it isn't really effective for a lot of use cases

and traceability that we had talked about earlier especially anything about traceback investigations where

if you have a perishable food you need to be able to know

when that you know you know where in the supply chain

that potentially compromised product sits and as fast as possible so

if you are even waiting a few hours at each of the supply chain junctions the critical tracking events,

it still can end up being a prohibitive amount of time to be affected in a traceback

and then subsequent trace forward investigation.

So this is kind of the vision of what the future of traceability should be, is end-to-end traceability.

This is really, there's some misconceptions about what end-to-end traceability really means, but what we're really entailing is a,

100

you know, industry-wide

101

or sector-wide approach to being able to enable the connection points to trace back products all the way to the source.

102

So this is more than just requiring food companies to keep information on their customers and on their suppliers.

103

It's also really kind of mandating a standardized way of housing this information

104

and setting up interoperability and data query mechanisms so that you can facilitate this trace back even among disparate information systems.

105

So, when you're designing, you know, a large-scale system like this, this is kind of like a system of systems, right?

106

You're wanting to kind of hone in on the core components of what you need to know

107

and what you need to design around.

108

So there's a couple of different groups of concepts here that are combined into one slide.

109

You have the key data elements and critical tracking events, and these are concepts

110

that were created by the Global Food Traceability Center in understanding how to provide recommendations to the FDA

111

when implementing FSMA's Section 204 provision.

112

And then we also have three other concepts on that are really come from GS1 on product identity.

113

So I'll actually now go into detail on all these.

114

So key data elements these are the key pieces of information

115

that need to be collected at each juncture of the supply chain so that you can address the use case.

116

So for food safety, this may just be information on the who, what, where, when, and why of the product so you can do an effective recall.

117

But if you're thinking about it also in terms of food quality or if you're thinking about it in terms of sustainability, you may be capturing other data elements.

118

So So for instance, when we work in seafood, catch area is very important

119

because companies are also concerned about potentially illegally caught product entering their supply chain and then being responsible for it.

120

So they may have a catch area or they may have the gear type or something like that.

121

So other key data elements can include temperature readings,

122

humidity, that sort of thing that also be aiding a particular company's quality indexes.

123

So critical tracking events are in work in conjunction with key data elements.

124

So these are the critical junctures

125

that I was talking about where you need to track the KDE's in order to address your use cases as well.

126

So not every event that happens in a logistical supply chain may be necessary to be captured for traceability reasons.

127

So and it depends on what your use case is that you are designing your traceability system around.

128

For recall purposes it's really being able to know when

129

and where the product is and

130

so really it's kind of centered on chain of custody

131

but for other use cases you may have you may have other CTEs.

132

These are broadly grouped into commissioning events, the origin of a food product,

133

the harvesting of the base ingredient, transformation, which takes inputs of particular logistical units

134

and transforms them into an additional one

135

so this is usually a processing step of some sort also aggregation events can take on this form

136

or commingling events sorry not aggregation

137

and then depletion is also the consumption of the product

138

and then the other three concepts that are really core are identification capturing

139

that identification and sharing that identification of that product identity

140

so what is very important to end-to-end traceability is the ability to have a globally unique identification schema

141

so for companies that work

142

and the processor sector forward to to the retailer they tend to use

143

and there's wide especially in the United States there's wide-scale adoption of GS1 standards for product identity this includes things like G10s,

144

serialized G10s, SFCCs for containers, and then also having GLNs,

145

the global location number for registering locations.

146

And these are captured through a variety of mechanisms.

147

These are the familiar barcodes that can take on the form of data bars or GS1-128 case labels,

148

or they also can take the form of QR codes.

149

And then also in the emerging spaces using RFIDs for capturing this information.

150

There needs to be a way to basically link the digital and physical realms and that's what this capture segment really entails.

151

And then the sharing platform and this is the sharing of business information across supply chain partners

152

and ensuring that information is kept on a need-to-know basis but it is readily accessible

153

in the cases of the need for traceability information.

154

In data sharing there's a balance between what should be visible and what is business sensitive and that is

155

is still being explored in what that proper balance is but

156

and especially in end-to-end traceability schemas but it is yeah anyway

157

so moving on this is kind of

158

when we're conceptualizing traceability of the design elements we basically put KDE's

159

and CTE's in a matrix where we have the who what where

160

when and why along the rows

161

and then columns of each of the critical tracking events

162

that happen this has been very useful because it can help you figure out

163

and conceptualize what needs to be captured at each of the CTE's

164

and what the because odds are you're already collecting

165

that each of the supply chain partners are capturing this information

166

but it may not be complete on what they have available

167

this also allows you to understand what format they may be

168

so some of these records may be digitized some of these records may be paper-based

169

and it allows you to devise a process flow for the products

170

that you're trying to initiate a traceability information traceability system in

171

and allows you kind of make strategic choices on technology adoption identifying identifiers

172

and figuring out which KDE's needs to be collected

173

so I'm gonna after talking about the the core concepts to traceability

174

and the basic vocabulary words

175

that we use in traceability space I want to kind of talk about how current traceability is a challenge um

176

and what are some of the drivers towards what the current trends you may be seeing in government along disability.

177

I kind of want to talk a little bit about, it's kind of in broad swaths, but about historical trends.

178

But just in general we are you know seeing you know localization of production of various commodities

179

and because of

180

that we also have extensive distribution networks to being able to deliver those those goods to the consumer readily available and cheaply.

181

So So there's been a lot of choices that we have made in order to make this possible.

182

We end up having fairly complex supply chains.

183

We have aggregation and co-mangling events that can make trace back to the source difficult.

184

And we also, because of the way the industry sits and because of the various players on those stakeholders' needs,

185

we have disparate information systems where some people may relying very

186

much on paper records still some are looking at you know fully digitized blockchain based systems

187

and so you have kind of a variability in adoption so

188

that current landscape can be quite tricky to navigate because

189

when you're designing a system-wide system you know you are having to anticipate

190

and design around those those variability's of heterogeneity

191

and then also I kind of wanted to speak to some of the scientific and outbreak trends.

192

So methods in, you know, that often when we're thinking about traceback investigations, we're thinking about kind of three principal stools.

193

So there's, or in food safety emergencies, we're thinking about three principal stool legs.

194

We're thinking about lab results.

195

We're thinking about the epidemiology linking lab results to the vehicle.

196

And then we're also then doing the traceback

197

investigation to identify the convergence point and to be able to trace forward

198

and understand where the potentially contaminated product may be so

199

that it can be removed from the shelves or removed from the supply chain to protect consumers.

200

So what we have seen in general is that you know lab techniques

201

and epidemiology have generally continued to improve and and continue to be able to discover lower and lower case count outbreaks,

202

we're able to, with whole genome sequencing, we're able to more easily link laboratory results with each other,

203

previously with, with the pulsatile electrophoresis,

204

we're matching up PFGE patterns, and we sometimes had false links sometimes missed links

205

but with WGS we're much more able to identify outbreaks as they're occurring

206

and long-term outfits as well and then epidemiology also continues to improve

207

and so as data collection

208

and also the clinical realities are changing too the physicians are

209

much better able to test for a variety of potential pathogens and also increasing the detection.

210

And then on kind of the more human side of this coin, we've seen, you know, social media really amplifying outbreak messages,

211

people being very cognizant of it and being able to share information very rapidly,

212

and this can have a greater reputational risk to companies.

213

And then, you know, with those two identifications of outbreaks happening easier,

214

much more robust and immediate data access is really necessary for an effective traceback response.

215

So, I kind of want to do a little bit of time check yeah

216

so i'm going to kind of quickly go through the romaine

217

one of the romaine uh the outbreaks of e coli 0157

218

and romaine last year this is the one

219

that um came out of huma um this uh

220

and just kind of illustrate how this is really showcasing why traceability is so important

221

and we have such a um you know we have a

222

challenge in front of us um as i said it was

223

very widespread multi-state outbreak with very serious illnesses with 45 with

224

HEUS the they could not pinpoint a single grower processor harvester

225

distributor there was not as I show later here there was not a convergence point

226

that they were able to identify in their various traceback investigation

227

so they had to brought they were able to they didn't

228

know what the you know what the pathogen was it didn't they did also know the vehicle, they knew that it was romaine lettuce,

229

and they did know the growing region at least

230

because of also I mean this is where romaine lettuce is produced at this time of year, but also in the Traceback Investigations,

231

they could not readily pinpoint exactly where it was coming from

232

and had to issue quite broad recommendations on not consuming any romaine coming from the Yuma region.

233

And so it also took quite a bit of time in real time to do these traceback investigations

234

and that was also very because of

235

that they had to keep amending their the regular regulators had to keep amending their recommendations to consumers

236

and their their their recall efforts which is also less than ideal.

237

Again this is kind of just summarizing it

238

and how it couldn't be resolved in real time

239

and where end-to-end traceability

240

and digitized standardized records could be a very it could be of extreme benefit in in aiding

241

or aiding this process

242

and one other thing that's touching why it's faceability is challenging

243

as I did it kind of alluded to this earlier is

244

that we have these really shiny objects that are occurring in digital technology

245

that are very promising but they also are not silver solutions especially blockchain

246

which I will talk about in depth a little bit later

247

if we have time but also artificial intelligence and advanced analytical techniques

248

and IOT devices all have these potential benefits to enabling indenture

249

its ability of having much closer data monitoring of having unified methods of sharing data

250

and decentralized approaches to data sharing but they are they do require certain elements

251

and that's why I taught started this talk talking about what the core things

252

that we need to know we need to know what those

253

key data elements are we need to know what those critical critical junctures where the data needs to be collected

254

and we need to have a unit we need to have an ability to have global uniqueness on the things

255

that we're tracking and without those elements none of these you know technologies

256

that are coming out are necessarily going to solve that

257

but they can if you are having a standardized approach and

258

if you are consider having a thoughtful approach to your design

259

that these can be of benefit but it does cloud the conversation somewhat

260

so that kind of leads me into really what GFTC brings to benefit for the global food industry

261

which is really having the ability to bridge various stakeholders to arrive at unified standards

262

and traceability and various good commodities and

263

so I want to go over some of the existing standards

264

that exist for product identity and traceability

265

and just kind of pointing you guys to tools

266

that you may be able or resources you may you may already be aware of them

267

but that you can look at to learn more about what the current thinking of

268

or what the current thinking is and traceability and what you can do to further your own education.

269

Really, for product identity standards and linking supply chain nodes, the Global Standards 1, or GS1,

270

has made significant strides in having a unified approach to global uniqueness on logistical units and product identity.

271

They have various working groups and standards that they work on to facilitate this.

272

So as you probably know they are known for the barcode

273

and the G10 and informing other various identifiers through the purchasing of a company prefix.

274

They are are deeply involved in various traceability efforts

275

and designing their standards around the ability to trace back various goods, including food.

276

So they have a fresh foods and retail working group.

277

They also have standards called the Global Traceability Standard, EPCAS, which stands for Electronic Product Code Information Services,

278

and Digital Link, which a new a new initiative to have to really utilize

279

the power of the internet to digitally link records together I will not really go into greater depth on this

280

because I am trying to be cognizant of time the produce traceability initiative is a traceability initiative

281

that relies heavily on GS1 standards evidenced by one of the major partners being GS1US.

282

The impetus to this initiative was the 2006 E coli 0157H7 outbreak in spinach in 2006.

283

So that kind of had this commodity killer effect where even companies that were not implicated in the outbreak had,

284

you know, decreased consumption and decreased business for years.

285

It took up to a decade really to get up to the same consumption that was at its peak.

286

So this is a North American effort primarily focused on the US,

287

Canada, and Mexico to have a unified approach to traceability so that they can trace back products to its to their source.

288

really they focused on labeling and identification and how that

289

and resolving real technical challenges that they have in the especially in the upstream

290

which is where it's most challenging to start global uniqueness

291

and identification and to have digitized records

292

and then finally the I'll talk a little bit about the global dialogue

293

and TV traceability this is the effort that we are currently working on.

294

We are working with an industry collaboration of 67 or 70

295

seafood companies across the world to develop a unified traceability standard and to address both food safety and illegal catch.

296

Illegal fishing is an extremely large problem in the seafood industry.

297

There, I think there's been some reports that up to a third of seafood is actually illegal or unregulated or unreported.

298

That's globally traded.

299

So, they had additional key data elements

300

that needed to be collected in order to ascertain that product is legitimate and is not fraudulent.

301

And we're seeking ways to enable interoperability between information systems.

302

So we used our methodology, which I'll describe a little bit later,

303

to leverage global standards that I previously talked about in order to have a unified approach.

304

And then finally, I'll kind of speak a little bit more directly to the regulatory side of traceability at the moment.

305

We do know with the Smarter Era Food Safety

306

that there's going to be a movement forward at the FDA for their approach to traceability.

307

And writing to that, when FSMA was put into law,

308

the first provision of Section 204 went to effect where FDA

309

contracted with IFT to facilitate an investigation basically of what is the landscape of traceability in the United States?

310

What steps does the FDA and the industry as a whole need to take in order to get from a one-up,

311

one-down system to a more connected and hopefully end-to-end system?

312

How do we conceptualize that in a technology-agnostic way?

313

And is there a way for us to move the needle a little bit in solutions to traceability?

314

So this was an extensive trace, somewhat similar to a traceback investigation,

315

understanding what the product flow from the source to the retailer was,

316

and understanding also the data collection needs and the information psychology realities.

317

Through this we produce a report

318

which is still being used heavily by a variety of stakeholders to move forward in building traceability systems.

319

So finally I want to go into the technology and applications

320

and traceability which really connects a lot of those key concepts

321

that I was talking about earlier and the standardization efforts that I was talking about as well.

322

again think about those fundamental categories of capture or identity capture

323

and sharing your identification you're thinking about any kind of unique identifiers digital identifiers capturing

324

that can also be capturing that identity through physical means

325

or through digital means also capturing additional key data elements that should be collected and then sharing are the

326

various data sharing protocols that exist this can be anything from advanced blockchain

327

or cloud-based systems to you know you know even mailed

328

or emailed records so just really the idea of sharing traceability information

329

and then also the use which is kind of newer in this space

330

but it's the reality is that as information collects or digital as data collection increases

331

we're going to be able to translate that into information and to analytics to

332

to better supply chains better efficiencies

333

and also better be able to respond to food safety incidents

334

so here's a little bit more information on identification

335

and what we really mean by that generally

336

and what you may be mostly familiar with our GS1 identifiers

337

it's usually the G10 plus lot to get down to the granularity needed for a recall response.

338

So GTINs are made up of a company prefix that a company purchases,

339

and then they form a unique class of identification for that product with the GTIN-14.

340

And then there's an associated lot, which is an internal identifier to put it with a batch lot production.

341

That can actually be incorporated into what is called an LG 10 or G 10 plus lot, which can be put on a label such as a GS1-128.

342

There are also non-GS1 ways of unique identification.

343

We're running into this often in our traceability piloting activities and in our divisement of traceability system of traceability guidance,

344

because the reality is that there's not a lot GS1 penetration upstream especially at the producer

345

and even up to the primary producer level there can be

346

a low amount of you know there may be internal identification

347

but they may not be using they may not be using a GS1

348

so where companies have made quite a bit of strides in

349

doing end-to-end traceability such as a lot of blockchain companies other

350

traceability companies they often will supply their own unique identifier

351

and their own with basically their own company prefix to

352

that particular supplier and then they use that internally but externally

353

when you're wanting to if you wanted to have a unified way of identifying

354

and ensuring that there's no collision between you know which basically means

355

that people are sharing the same identifier you you IDs is also another way of doing

356

that and then encoding that

357

that identification should be on is generally done on optical through optical means namely barcodes again

358

because of the amount of GS1 adoption and associated with that

359

that means there's also a lot of readers a lot of automated ways of picking up that

360

QR codes are also on the rise not as much especially in high throughput circumstances

361

but QR codes can be generated

362

and hold of more information than what a barcode can can hold

363

and have a little bit more flexibility

364

and are a little bit more durable there are also advances to using RFIDs

365

which are radio frequency identifiers which have advantages in

366

that you can read them at a distance you can also

367

read multiple units at once you can basically you know pass you know pass product across an array

368

and would automatically read it there's been some implementation challenges with

369

the sorry my the light the automatic light my room just turned off anyway

370

but but they are also there's being more adoption and that and then there's a couple of other experimental

371

machine readable identification mechanisms that have not borne out yet

372

but they're on the rise so data capture again

373

so I was talking about earlier that there's associated KDE's that all need to also collect that information be and

374

house it with and associate with that unique identification this is important to our efforts

375

because these data need to be collected in a standardized

376

and digitized way so that there can be interoperability between systems so

377

if someone is a basic you know basic thinking around this

378

is like how would you house you know temperature readings do how's it

379

and you know generally at Celsius but you want to make sure

380

that all supply chain partners are using Celsius you also would

381

want to have a you know standardized the word I'm looking

382

for have a standardized amount of digits to the specificity to the temperature things such as

383

that so mostly like arriving at the unified syntax

384

and semantics of the pieces of information and then having best collect best practices around that collection of information.

385

So anything really can be considered in this segment, but mainly it's the capturing of the identity and then the associated KDE that needs to be collected.

386

And then data sharing.

387

And this is really important to business providers

388

or solution providers and their corresponding food companies that they're working with for food safety regulators, it's important to kind of know these concepts,

389

but it's not going to necessarily be part of your specific needs and traceback.

390

But this is kind of where there's been a lot of excitement

391

because there's classically been these ways of sharing business information especially along electronic data interchanges

392

but you know with the enabling of the Internet's HTTP s API's are very popular

393

and then blockchain also as a mechanism for sharing data

394

across the fly chain nodes is also very popular and I won't go into that much detail with this.

395

So this is just kind of a it's kind of a

396

nifty graph it's I know it's a little bit cumbersome

397

and a lot of words but what I really want to center this focus on is

398

that standardization really especially in the food traceability space really centers on this this line of sharing

399

and capturing really in the EPCIS capture interface that's really the

400

EPCIS is just a file format for encoding logistics information

401

and standardizing that approach for the use case of the industry is really important

402

so that you can really use other standards

403

and protocols you know at the data capture level

404

and at the data sharing level to leverage and enable

405

and then traceability and then finally I kind of talked about this in the introduction

406

but there's you know the actual use of the traceability information how should it be housed

407

and shared so that we can have these affected

408

so we can actually use information for what we want it for

409

so in food safety

410

and trace back investigations you this may be the principal data

411

use is going to be you know rapid query ability in the event

412

that needs to be so for sustainability maybe being able to do audit checks

413

or be able to perform a mass balance to ensure

414

that there's the allocation

415

that all of the weight of the product is accounted for throughout each supply chain network

416

and also though once you have an you know information

417

and aggregator along the supply chain no matter you know

418

if you have more

419

and more information about further upstream of your supply chain you

420

may also be able to make better decisions about your purchasing

421

or how you do inventory or and also

422

that can feed into your your food safety considerations as well

423

and then again there's the kind of this balance between accountability

424

with business sensitivity we have seen a shift oh from businesses

425

being extremely sensitive about what is shared to a little bit more of a nuanced approach to

426

that they realize that transparency in supply chains is going to rise just from happenstance

427

and the advancing of technology and these advances in these standardization efforts etc

428

but that does need to be balanced with the particular information

429

that may be critical to what gives them a market advantage

430

um just a kind of a take-home point is

431

that you know we have found that standardization to data elements

432

and IT architectures is critically important to enabling indent traceability

433

and enabling solutions to to arise

434

so what we really see standardization as is kind of common rules the road where technology providers can come in

435

and use those common rules the road to really basically compete

436

on user interfaces on their ability their you know data security

437

you know all these kind of technical considerations rather than you

438

know trying to garner market share in using their proprietary data format or their proprietary way of labeling or

439

or issuing identification the future technology may change may change the the realities of traceability

440

but at the moment this is the what we have seen

441

and it will be the reality for some time especially as producers become more

442

and more digitized but that's still um that's still on the on the right

443

so I just kind of want to talk specifically about blockchain you guys may have heard about it

444

and I kind of wanted to spell kind of some myths

445

some of the mythology behind it um I want to kind of

446

and I'm going to keep this pretty short um

447

but it has been kind of of tatted as this ultimate ledger

448

and data sharing arrangement where everybody has a decentralized copy of the ledger

449

that sensitive information can be cryptologically you know hidden

450

that there can be variable you know levels of access using smart contracts etc etc

451

because of the way of its architecture

452

it's um it's uh uses time stamping and encryption

453

and linked records to to ensure that there's this immutability um

454

and uh so because it has this kind of decentralized approach

455

and because it you know just is a very promising technology in general

456

and has certain attributes um

457

that has seen have been seen as a very attractive technology to be used in food traceability

458

I will preface this with the caveat being that blockchain is a technology that's born out of the financial technology space.

459

So it works very, very well in Bitcoin and Ethereum and trading digital assets.

460

When you're trading assets on a blockchain that only sit on the blockchain, it works very, very well and but when you are tying

461

that to a physical asset is still a lot of these problems that I was talking about earlier about standardization about

462

digitization about you know interoperability still still occur

463

and are still meaningful additionally you know with the technology still

464

in its infancy there are issues with latency you know a long period of time between posting a transaction

465

or posting a data upload and it actually being appended on the blockchain

466

because it has to be resolved among all the nodes.

467

Error correction can be a problem because it's immutable it's not really it's not something

468

that you can actually go in and delete or amend it.

469

You basically would have to and

470

then there's also level visibility at the moment a lot of blockchains are mostly set up for fairly radical transparency

471

and then you still also have some regulatory considerations such as GDPR

472

or our gas requirements are requiring the use of cryptocurrency to

473

upload something onto a public blockchain those are a little bit less relevant to us

474

because we're in the United States and we're not necessarily thinking about GDPR

475

and the gas requirements is a consideration for Southeast Asia but it's also as important to note that it's

476

some cryptocurrency is still being explored by various regulatory entities not just food safety

477

but and financial assets as well

478

so I kind of want to give you guys some food for thought on how to on what some tools

479

and techniques would be useful for you you know really centering on familiarizing yourself with data standards is really something

480

that could be really useful to you.

481

The global traceability standard for instance at GS1, but looking at also the produce traceability initiative

482

and their approach to standardizing case labeling

483

and also looking at the IFT FSMA report may also be very useful in and thinking about a system-wide approach to traceability.

484

And then also kind of investigating some of the digital aspects of it.

485

Really, I don't think these are necessarily skills that are required, but in the future,

486

having a little more digital slaviness is going to be going to be essential to being effective in traceback investigations,

487

being familiar with SQL queries,

488

being familiar with various file formats and how they're transmitted may be useful to you,

489

and also kind of understanding where the industry is and what their current, what their next steps are in designing traceability systems.

490

And I can share some of those some of those resources as well in a post-meeting email.

491

So with that, that's kind of a rapid look at traceability,

492

what we've seen in our effort as a convener of global industry players

493

and where that interplay is between what the industry needs are, what the regulatory needs are,

494

and what various interest groups such as sustainability NGOs or food safety advocates,

495

and converging those into having a unified standards process.

496

I think we have about 10 minutes available, and I will leave it to Randy to help us, lead us through the questions that have arisen.

497

Thank you.

498

I think we have a question here from James.

499

And the question is, what is the most critical component of traceability in produce safety?

500

So, what we've seen in the most critical component is really the identification

501

and the integration between that identification at the harvest level and at the commingling level. been there

502

because of the business realities at the harvest level it is not easy to implement a new process

503

or to implement a new labeling requirement that can uniquely identify products

504

and there's also challenges once it can get to the pack house where coming events may occur

505

so that's still really the biggest challenge

506

that we see is you know uptake of identification schemas

507

and in compliance to a standard so

508

that there can be better better trace back to the source I don't know Brian if you have any additional thoughts

509

no I think that's appropriate you know the the protus industry has been on quite a journey

510

and they've been learning a lot.

511

Thomas highlighted a couple areas that they continue to work through and try to drive industry level type of alignment.

512

One of the challenges in this space is getting to a common language

513

and a common set of tools that can be used by everyone in a pre-competitive type of environment.

514

Certainly the produce industry has been on that journey and continues to be on that journey.

515

I'd like to go ahead and thank Brian and Thomas for making the time to present today, and I'd like to thank everyone else for attending.

516

And that will conclude today's webinar on traceability.

517

Thank you, everyone, and have a great day.

518

Thank you.

519

Thank you.

シャドーイングとは？英語上達に効果的な理由

シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。

シャドーイング練習: Traceability 101: An Introduction to Food Supply Chain Traceability - 動画で英語スピーキングを学ぶ

このビデオは誰におすすめ？

覚えておきたい単語とイディオム

アクセントのコツをつかもう

シャドーイングとは？英語上達に効果的な理由