And somebody has to model those relationships as part of that.

It was four or five years ago, I was invited by Flexware to join a Sesame conversation.

Sesame was coming to Fishers, Indiana to present, and I drove up.

Scott was kind enough to open up the shop for me, and I heard John Dyke and Jonathan Wise kind of lay out the three imperatives for the first time, and it was imperative number two, instantiating from those standardized imperative one models with context and relationship.

And that was the moment where Graham and I came together and said, they've got the map in place here.

Sesame's giving really good advice.

his object-oriented programming background, what they were saying, and the fact that we knew we were gonna be building a new modeling product, Timebase, we said immediately, relationship, relationship, relationship.

We can just go back to this system that's really the source and tells us where to go get everything else.

That's what Jeff was referring to right here.

So the conversation with one of the largest frozen dessert manufacturers in North America is, Multiple sites, which means multiple SCADA systems, multiple MES, multiple ERP, actually.

And their question to me a couple days ago is, hey, I've got these two leading integrators in the country.

I mean, these are great integrators.

I'm getting ready to approach them on doing this job.

I said, what do you want? I want a UNS that's queryable.

I want a UNS that is AI-enabled.

And, and the second question was what, what was the second question?