R
Ryan Crownover
1
APPEARANCES
1
PODCASTS
012
DEC 30
JAN 6
JAN 13
JAN 20
JAN 27
FEB 3
FEB 10
FEB 17
FEB 24
MAR 3
MAR 10
MAR 17
MAR 24
MAR 31
APR 7
APR 14
APR 21
APR 28
MAY 5
MAY 12
MAY 19
MAY 26
JUN 2
JUN 9
JUN 16
JUN 23
JUN 30
JUL 7
JUL 14
JUL 21
JUL 28
AUG 4
AUG 11
AUG 18
AUG 25
SEP 1
SEP 8
SEP 15
SEP 22
SEP 29
OCT 6
OCT 13
OCT 20
OCT 27
NOV 3
NOV 10
NOV 17
NOV 24
DEC 1
DEC 8
DEC 15
DEC 22
DEC 29
JAN 5
JAN 12
JAN 19
JAN 26
FEB 2
FEB 9
FEB 16
FEB 23
MAR 2
MAR 9
MAR 16
MAR 23
MAR 30
APR 6
APR 13
APR 20
APR 27
MAY 4
MAY 11
MAY 18
MAY 25
JUN 1
JUN 8
JUN 15
JUN 22
JUN 29
JUL 6
JUL 13
JUL 20
JUL 27
AUG 3
AUG 10
AUG 17
AUG 24
AUG 31
SEP 7
SEP 14
SEP 21
SEP 28
OCT 5
OCT 12
OCT 19
OCT 26
NOV 2
Oct 21, 2026
Why the Knowledge Model Is the Missing Layer in Your Industrial Data Architecture
32:27

Travis CoxHOST
And that's not necessarily put into the control system, right? And so what does a stack really look like? And maybe Ryan, we start with you, because I know this is something that you fundamentally had to figure out yourself, right? How do you build this? There's, you know, this system, the ignition's in place, but where do you go from there?
R
32:45Ryan CrownoverGUEST
And, you know, the the need that we've seen and I'll start that off and that we shared with with the flow team early on in the journey for for time base is that we've got five fun.
R
33:00Ryan CrownoverGUEST
At least we look at it as where we've got five different fundamental types of data.
R
33:04Ryan CrownoverGUEST
We've got our real-time values, right? Those go through ignition tags and other systems like MQTT, etc.
R
33:11Ryan CrownoverGUEST
We've got historical values or telemetry that are often connected with and associated to those live values, but they need different storage mechanisms than those live values.
19 MINS LATER