Reliability Radio EP 377: John Craig

So that's a definition, right? Nothing wrong with that.

Now let's take that a step further.

Let's say you actually get to there, right? So for those in the audience that...

There's this perception that most of the time, engineers and management think this is already done.

Just walking into a space, just setting it up, somebody's already gone through that effort.

How do you go to somebody and tell them your data's ugly? And you got to spend some time to have people walk around to tell you what you have.

I would imagine from my own experience that managers don't like hearing that.

How do you deal with that?

It's difficult to do.

But again, there are generally opportunities where the data will support what you're saying.

Obviously, what's missing, you don't have.

So you really can't speak to.

But often what is there is telling a story that says something's not adding up here.

So generally my experience, especially when I'm speaking with our clients, they're fairly aware that their data is not very pretty and it's not complete and often it's not standardized.

And I think that comes from an idea that they've probably done this before, right? Or they've assumed they've done this before and they're probably wondering why they have to do it again.

Yeah,

well, as they're running into those problems, they realize, yes, someone's done this.

The data exists.

But why isn't it

being kept up?

As I'm running into a problem in this area and I have this equipment that's failing, I also have it elsewhere in our facility.

And when I'm looking to compare that report or in a report that information, the system is not helping me and saying, hey, you have this 25 places.

It's saying you have it in five places and then a like system, five more places, another like system, five more places.

And rather than having it pulled into a single report, we're now reporting on just small subsets of similar class assets.