WEBVTT

1
00:00:05.000 --> 00:00:17.000
<v Josh>Welcome back to another episode of Facilities Unfiltered, the built reality where we navigate the space where theory meets real world chaos. Sponsored by AkitaBox. I'm Josh.

2
00:00:17.000 --> 00:01:43.000
<v Nic>And I'm Nic. Welcome back. Josh, today we're going to keep it first grade simple. We'll try. We as an industry, we as ourselves, if we're being completely transparent about it, I think tend to overly complicate sometimes what we're trying to achieve and what we're trying to deliver. And I can tell you, having received an FCA or even any kind of study in facilities, in trying to go to a board, just imagine me sitting up there, late 20s, early 30s, nervous as all heck, 10 board members up there and I need $5 million for D50 and I've got to do a 10 minute speech and explanation of what D50 is when they just wanted me to say I need $5 million for HVAC. Right? And I've done FCAs. Right. And I've done them super granular down to the wall coverings, done them in any kind of format and super spelled out. So not claiming any kind of soapbox here, but also want to kind of identify and just call out something that I think is worth conversation.

3
00:01:43.000 --> 00:05:01.000
<v Josh>Yeah, and I think you were rightfully calling ourselves out, right. We tend to get over academic with it as well, especially when we can geek out about like, oh yeah, you can get down to this level and have this different standard of data points at this level of Uniformat, and you can customize your level five. And you know, I sit on an ASTM committee for, you know, putting together the FCA standards. Like I like standardization and I like having things you can point at and go, it's always going to be the same. But the problem becomes, as we sit in those rooms by ourselves, not out in the field, not out with people who are going to be collecting the data, and we start to say, whoa, that's really complex. And then we go, yeah, but it's actually not complex enough because you just missed these 40 other things and you end up adding another layer of complexity to account for those. Because from an academic standpoint, classification, right. I mean, if you take it down to what they're really trying to do, it's like botany, it's like going out and looking at animals and how you classify things in nature and science. And we're trying to apply that to a built reality that we've made a mess of. Right. There isn't a natural order of classification for these things — we just make them up out of the unnatural world. And we're still trying to apply that science to it. And to your point, it's never first grade simple because in order to be complex and in order to classify something you have to be able to identify its differences. And that's where I think we start to run into problems. And I'll use — I went and did some research on this. Right. Because that's what we do here is we try not to just say our opinions all the time, even though we do that too. But we try to at least have the conversation around some sound numbers and talking to people. This isn't just like hey, we went out and got numbers. But talking to people who do this. Right. Our customers go out and do condition assessments and collect data in things like Uniformat II or CSI format or some other standard. And they'll tell you to get somebody trained. Sure. You can teach them the basics. D50. Right. Like all the first level groups, the nine major things, the 35 elements. Right. We can do those in a couple days. But when we get into actually collecting data, actually doing something where we're classifying down, if we're just at a level three, that can take you three to six months of field work. That's time that you're paying somebody, and time that they're supposed to be creating a deliverable for somebody and they're still trying to comprehend where something goes. Right. And if we go beyond that to a three and a four, which is frankly where most of the asset level classification lives, that's one to two years of field work to become proficient. Right. At least probably on the major things. And you still probably scratch your head on some of the alternate things. How do you scale a team on that?

4
00:05:01.000 --> 00:06:48.000
<v Nic>Well, and that's all under the assumption that they know building systems. [00:05:07] Josh: Well, you hit the other point real quick, right? Yeah. [00:05:10] Nic: Like how many condensing units get classified as a heat pump or vice versa. Right. Like that in itself takes time. And it seems like during our onboarding and our training process, that's more where the value is — proper identification of systems and system application so that we have good data, not how do we... [00:05:33] Josh: How you file it is secondary. Right. Yeah, yeah. So, and I'm not — I mean we are here to poke the bear a little bit because why else would we do something like this? But no, it's for conversation. Because to your point, the conversation needs to be we're in a new day, right. Today is not yesterday and AI is here and it's real. And AI is really good at filing stuff. So is this a magical time where we can embrace and actually allow the academics to get even geekier? Go ahead, make it as different as you want and create as many classification buckets as you want and be able to, from a data perspective — and I understand the value of that. Especially when we look at mega data sets and we look at like the government and the GSA and how do they actually look across their billions of square feet and roll anything up unless it is a very strict standard and they can get down to the granularity. I get the value. But for the average person who owns a building, runs a building, sits on the board for a building, D30 means nothing.

5
00:06:48.000 --> 00:08:16.000
<v Nic>Yeah, no, I mean, at the end of the day, this is supposed to be a usable document that either the facility manager or Frank, Sally, whoever it is, can go to the stakeholders without having to hold a seminar before giving them an explanation on the classification structure. Right. Like this needs to be transferable to an audience that doesn't live in our world. And I think that's where we get held up sometimes. I mean, you look at these reports and the methodology just in data collection and the secret sauce of how they're doing risk measurements and stuff — those can be pages long beyond just the classification system. So there's already complexity and if [00:07:32] Josh: we're honest with the industry and the industry's honest with itself, things get misclassified all the time. Because it is complex. Right. And so — ultimately, if I'm in the field and I'm being held accountable for how many assets I need to collect and I just walked up to a chiller and I found pump. Oh, it was a heat distribution pump or it was a boiler feed pump or it was something else. Like I'm just going to find pump and we're going to move on 90% of the time. Right. Especially if I'm under the gun and I'm feeling the pressure. That's where having that one to two years of experience to know, okay, here's exactly how I flow down and find that exact pump. But you're not getting that day one.

6
00:08:16.000 --> 00:08:21.000
<v Nic>Yeah, no, absolutely. I mean, I was always just a fan of just calling it pump.

7
00:08:21.000 --> 00:08:22.000
<v Josh>Right.

8
00:08:22.000 --> 00:09:15.000
<v Nic>Because there actually is no just straightforward pump in current classification. You only find that. So you just got to kind of wrap it up. But yeah, no, I mean, I agree with that. I think it makes training easier, it makes our time more valuable. I'm thinking about, you know, some of the young people that I worked with training and doing this and how long it just took to get them up to a place that was reasonable for data collection, so we were semi profitable. Right. Because in those training periods I had a fairly young team and we were, you know, a lot of entry level people. It wasn't very profitable for us to go out, but we understood that as business and we were okay with that. But to your point with AI, how much more efficient could we have been? How much more profitable could we have been? And yeah, the classification is great as an underlining mechanism to roll things up.

9
00:09:15.000 --> 00:10:23.000
<v Josh>And one of the best analogies that I can think of here. Right. If we want to talk about how silly this is to some degree — it's like walking into a library to find a book and the librarian looking at you and going, that's cool. Before you can go find a book, you need to memorize the Dewey Decimal system and its classification so that you can go find what you're looking for. The library has the first grade simple and it's got the librarian classification, Dewey Decimal. That's a very complex thing and there's a reason why we don't make the general public understand and learn it — because I just need to go look for what I'm looking for. It'll tell me what section I need to go to. Fine. I'll finally get to the number and I know when I'm in the section I'm looking for this number. Cool. But you don't expect somebody to go find the section and everything else based upon that number. Right. And so I think that's where this is falling down. We're actually asking the technicians — in order to do your job, in order to go find that book you're looking to read, you need to actually memorize the classification system.

10
00:10:23.000 --> 00:11:18.000
<v Nic>I would take it a step further — and beyond the technicians, the deliverable recipient and the audience that is getting spoken to needs to understand the risk measurements of the prioritization scales. Right. Because those can have a lot of complexities and I'm an advocate for that. I know we both have talked about advocating for multiple variables to help make a priority. Right. But how does that get spelled out and communicated to our end users? Is it a methodology that they can easily go, yep, that makes sense, I can communicate that. Or does it take two or three pages of the report for them to understand and then have to be able to regurgitate that to the stakeholders? So what makes a priority one, and that you need $5 million for HVAC — I don't want to have to go through this long list. It needs to be quick and first grade simple.

11
00:11:18.000 --> 00:12:08.000
<v Josh>Absolutely. And to your point, the people you're doing this for — it's not just the technicians who are in the buildings every day. It's people who, let's face it, may not even think about that building that often. Even, especially if you roll it down even further to the general public. When you talk about public facilities and school districts and those types of things, like now you're trying to get the general public — who you're trying to get to approve funding — to understand D30. Right. And I know that's the job of the architects and engineers that they hire is to help the public understand it, but that should tell you something in our process — that you need to hire an extra consultant to help the public understand what we just went and spent a whole bunch of money gathering.

12
00:12:08.000 --> 00:12:11.000
<v Nic>The best example of this is FCI.

13
00:12:11.000 --> 00:12:13.000
<v Josh>Oh, absolutely.

14
00:12:13.000 --> 00:12:53.000
<v Nic>Building health. Right. Like you're K-12 or your government and you need to go out and talk to a public body. And now you have to explain why good is low and high is bad, especially in the academic world, to educators. And so I love that Facility Condition Score — FCS — is now a thing, or at least we're hearing it's a thing, where we're flipping that metric upside down. Like, to me, that just makes sense. So I think looking for more of those easy buttons that we can press so that it just is more transferable and usable and explainable really is the point we're getting at here.

15
00:12:53.000 --> 00:14:06.000
<v Josh>Absolutely. And we want to make sure — and I want to make sure because again, I'm that academic geek who loves to over-classify things in order to get to that academic answer of, you know, which things are failing us more and what type of thing is failing us more and what size of thing fails faster than the other size of thing. All of that really refined classification helps us get super geeky about the data. But the average person, the average user, they just want to know that it's cold or it's hot, and if it's hot, I need to deal with the cooling system. And these are the things that are part of the cooling system. Or if it's cold and I need to warm it up, this is a heating system and these are the components of the heating system. In a lot of ways, that's the approach that frankly the facilities teams take, Nic, a lot of the times. And I know that that's how, at least when I was living in facilities teams and helping onboard our CMMS, that's how they talked about it and trained for it, and actually a lot of times that's how they organize their maintenance teams and trades teams — to focus on a system of the building and become specialized in that so that they, especially in healthcare, could triage much faster because they were specialized.

16
00:14:06.000 --> 00:15:22.000
<v Nic>Yeah, yeah, no, you usually have your HVAC technicians, electricians — when you start to get at scale, of course — but you have those specialty people. Low voltage is probably the most lucrative out there for anybody thinking about getting into trades. Low voltage for maintenance work is just way out there. But I think to your point, this is where AI really can help. Right. Like beyond the data collection, we have this great analysis that's done and then — forbid it's a static document or an Excel sheet — if it can go into a system and you can just start in native language, plain language, asking AI, what are my priorities with this amount of funding and why? A fairly simple question and it can start to spit back to you. Okay, cool. Now should we cancel preventative maintenance on this? Great, right. It can start to take the place of these two 300-page reports. We still need the data backing it and it still needs to be accurate. But people can ask the questions and do the analysis in their own comfort zone of how they understand information.

17
00:15:22.000 --> 00:16:39.000
<v Josh>Absolutely. And ultimately, you know, frankly, the computer sometimes is the only one that wants to know the Uniformat classification so that it can run its own analysis. To your point, the end user just wants to know, hey, it's going to be a rough winter. What condition is my heating system in and do I have any backlog maintenance that affects my heating system. I don't care what D classification it is. Right. I just want to know what's in the system. That's it. What's its function, what is it? And as you said earlier, I mean the thing that's hardest is being able to walk into a room and go, that's a heat exchanger, that's a unit heater. Oh, that's an air dryer. What's an air dryer? Because look, some of these systems have been around forever. I mean, talking about pneumatics, right, versus non-pneumatics. And when does a VFD come into play and when doesn't it. And you go into these old buildings and there's no VFDs. Right. So just being able to understand how buildings are put together, why the age of the building may matter in how you're approaching looking at it, and knowing in the back of your head that hey, this thing is pre-1950 — I'm probably not going to be looking for these components unless it was remodeled since then.

18
00:16:39.000 --> 00:19:06.000
<v Nic>Yeah. And don't get me wrong, I'm a fan of an acronym. Who isn't in this industry? In any industry. Right. Technical terms, we all like it. I remember being young and being really impressed by people that knew all these technical terms and acronyms, but it just doesn't show well. And it reminds me of — I took over this job and the CFO handed over this FCA that was done by a major FM provider. And she goes, I don't know why we need to spend $600,000 on cladding. I don't even know what that is. Again, that's a technical term that we in the industry get. But she just wrote that off and it was 10 years deferred. I can tell you when we actually went to go replace it, it looked like it, and it cost a lot more because she couldn't understand it. Like, I don't need this. I'm not going to allocate that money for that. So I think this is where we're getting at — some of the issues we've identified in the past about the usability, the maintainability, and the trust in these studies could come down to just that. Keeping it simpler or having a mechanism such as AI to help people keep it simple for their understanding. [00:17:49] Josh: Yeah. I mean we have the opportunity now, more than we've ever had before, for the data to meet us where we're at and fill in the gaps. Right. And this goes to data collection. Frankly, the idea of having to memorize and take one to two years to be proficient at putting something in a D3040 versus a D3050 and knowing how to get there efficiently — as long as you know what it is, AI should be able to do all the background classification, and that training component should become a non-issue. Using tools that have the ability to navigate those waters and allow you to be first grade simple on the front end. And don't get me wrong, you still have to have some knowledge. You still have to be able to walk into the room and say that's a heat exchanger. And AI can still help us with that a little bit. And in the future maybe you just have to know that I walk into the room and that thing's important enough to take a photo of, and it helps me get there. Maybe we'll get there in the near future. Right. But you still have to have some knowledge behind going in and knowing that I'm going to go take pictures of these 10 things and walk out. But AI can do 90% of it until you get down to maybe some judgment calls. Yeah.

19
00:19:06.000 --> 00:19:16.000
<v Nic>I mean, I think there's still a lot AI needs a professional for. You're not going to go do finishes with AI. It can't scale. Right.

20
00:19:16.000 --> 00:19:26.000
<v Josh>You're also not going to know multi-zone versus single-zone. And there's a lot of nuance that you have to turn your human brain on and maybe go look in some other places.

21
00:19:26.000 --> 00:20:19.000
<v Nic>So it's going to allow the people doing the assessments to really excel on their professional expertise rather than going through a classification system that they're still halfway learning. Right. And that is going to become more accurate, which we have beaten to death as being one of the biggest problems in the industry, especially around data and anything facility management. So I think, you know, the overall message of keep it first grade simple is underlining with use your tools. I mean, we have the tools to do it. We have automatic nailers. Right. A nail gun. You don't need to put roofing on with a hammer anymore. So use what we have in front of us.

22
00:20:19.000 --> 00:24:27.000
<v Josh>Yeah. And if you don't have a tool, go find one. Right. I mean, if we're looking at the industry as a whole, I mean, there's been a whole lot of data collection done in Excel. It's not going to cut it anymore. Right. Hand-entering serial numbers and those types of things aren't going to keep you competitive and it's not going to keep data accuracy up where we need it. And so, yeah, finding tools, using tools, getting yourself positioned so that you can still classify — but keep it first grade simple. I think that's really important for folks to start to explore. Right. Because the future is coming fast and if you're not starting to kind of look around and go, do I need to train people for one to two years and potentially be inefficient in the process? And do I keep those people after the one or two years of training and do I start the cycle all over? And so how do we shortcut that? How do we scale better? How do we just run our business better? Not saying again, the standard's not broken — it's just the interfaces. [00:21:22] Nic: Yeah. And don't get me wrong, we love standards. Right. Super excited to see the FCA standards come out. Love all this technical detail. I just think there are tools out there. And really, I had to ask myself the question — and I think a lot of us in the industry do — how do we make this more usable? And to me, I will just keep repeating it. Just keep it first grade simple. I had a mentor a long time ago who told me I was being way too technical in construction meetings and talking to stakeholders, and it's some of the best advice I've ever gotten — just make sure that you're not speaking over your audience. And I think because this data is so complex and the nature of our industry is so complex, we really get in the weeds and we really enjoy that. [00:22:10] Josh: And let's not let that get in our way. Right? [00:22:13] Nic: Absolutely. Yeah. [00:22:15] Josh: It's the whole — and I think we just, as humans, we have this pattern, right? And I see it. Both my parents were teachers, and they used to tell me when I was growing up, you need to memorize everything, right? You need to memorize your math because you're not going to have a calculator with you everywhere. Guess what, folks, right? And now with our kids, you need to go do research the hard way. You're not allowed to use AI. Come on. Like, at some point, we have to give in. And let's not make — right. Let's not make memorizing our Uniformat level two our version of, you need to memorize your multiplication tables because you won't have a calculator with you. We need to make sure that we're not being our own worst enemy when growth and opportunity is in front of us. [00:23:08] Nic: Yeah. And I think we're seeing the trend, right? I think anybody listening recognizes, hey, if we haven't already, it's already percolating in their head. They're already seeing it — just to be competitive, yet alone to put together a more usable deliverable. Or if you're an FM, you know, a tool that can help you speak better to the audience and advocate for the facilities. To your point, I mean, me and my family, we call it the answer box, right? Because my son — he's 7 years old — he's just firing off questions left and right. Dad, just look it up on your phone. [00:23:45] Josh: Yep. Yep. [00:23:47] Nic: And thank the library for that. [00:23:50] Josh: Back in the day, Nic, in Chicago, there used to be a number that you could call in to get sports statistics because they realized that the ability to know — right — then cut down bar fights in the city. So we've known for a long time that getting answers instantly is a good thing. I think one thing too is we all got a little smarter when we could go look that up. We were no longer going, well, I thought it was this and I'm right, and you thought it was this and you're right, and we just walked away agreeing to disagree. When was the last time you heard that in modern times?

23
00:24:27.000 --> 00:24:56.000
<v Nic>Right. [00:24:28] Josh: Are you going to agree to disagree with your kid on a fact now when you can go look it up on your phone? [00:24:33] Nic: No, no, I go to the answer box. [00:24:35] Josh: And we know. So this is kind of my point in a roundabout way. I actually think what's going to happen is that all of these people using the tools that do auto-classification to help them get to that filing system — they're actually going to learn the filing system maybe better and faster than they ever learned it before when they had to manually do it.

24
00:24:56.000 --> 00:25:16.000
<v Nic>I couldn't agree with that more. [00:24:59] Josh: So I don't know if I have much else to add to that. I think we've beaten this one down, Nic. But I do think there's a huge opportunity in front of us here, and the industry frankly has a chance to actually adopt a standard more holistically by maybe keeping it first grade simple on the front end.

25
00:25:16.000 --> 00:25:39.000
<v Nic>Yeah. [00:25:21] Josh: All right, sounds good. [00:25:22] Nic: Leave it there. [00:25:23] Josh: Well, with that, I appreciate everybody joining. Hope that you join us next time and stop fighting fires, start managing the heat.
