What are one or two things that they really should take as a lesson from what you're seeing in brewing?

Yeah, so I think first they've got to start on the data capture.

They're already behind on that part.

And they've got to capture the data and contextualize it right as they collect it.

That's the key.

A bunch of data in the database doesn't do any good if it's not contextualized.

So that's the most important part.

And now this might be a crazy question, and maybe in our many, many discussions, I may not have asked you this before, but do you think in the world of beekeeping, of all the world, are there lessons from that for us in

What were some of the biggest perceived risks, whether that was product quality, uptime, or operator trust? And how did the team address those concerns? Also related to those risks, how did you ensure stakeholders were confident that production control would not be compromised?

Well, I guess the biggest perceived risk and, to be honest, the biggest real risk was now needing not only the automation system to be working correctly to make the beer, but now you needed the MES system to also be working correctly because we were introducing another point of failure.

We implemented an OPC UA interface between the automation system and the MES system, but now that's a critical interface.

It has to work.

So we had to come up with a way to still make beer if that interface stopped working for a time.

We implemented data buffering directly in the new MES data harvesting function blocks in the DCS so that we could tolerate that MES to DCS interface being down.

For some period of time, we just set an hour.

First, automated data capture.