Learn about NexusCon!
.png)
"Maintenance needs to have a really integral role in this tool. And so the more it looks like their day-to-day hot and cold call, the better it is, right? So if we can make that push of that FDD resolution look like a work order, then it's much easier for the organization to adopt it. And I really believe that was integral to our success."
—Katie Rossmann
Welcome to Nexus, a newsletter and podcast for smart people applying smart building technology—hosted by James Dice. If you’re new to Nexus, you might want to start here.
The Nexus podcast (Apple | Spotify | YouTube | Other apps) is our chance to explore and learn with the brightest in our industry—together. The project is directly funded by listeners like you who have joined the Nexus Pro membership community.
You can join Nexus Pro to get a weekly-ish deep dive, access to the Nexus Vendor Landscape, and invites to exclusive events with a community of smart buildings nerds.
Episode 144 is a conversation with Tom Moore and Brad Dameron from The University of Iowa and Katie Rossmann of Clockworks Analytics.
Episode 144 is the first episode in a new series diving into case studies of real life, large scale deployments of smart building technologies. For this first episode, we talk with the University of Iowa regarding their integration of FDD via Clockworks Analytics. This project started in 2014 and includes 6.8 million square feet across 47 buildings. We hear the project team, the rollout, and key inclusion of their maintenance operations from the ground up.
Music credits: There Is A Reality by Common Tiger—licensed under an Music Vine Limited Pro Standard License ID: S441934-15083.
Note: transcript was created using an imperfect machine learning tool and lightly edited by a human (so you can get the gist). Please forgive errors!
[00:00:00] Katie Rossmann: Maintenance needs to have a really integral role in this tool. And so the more it looks like their day-to-day hot and cold call, the better it is, right? So if we can make that push of that. F D D resolution look like a work order, then it's much easier for the organization to adopt it. And I really believe that was integral to our success.
[00:00:24] James Dice: Hey friends, did you know the best way to continue learning beyond the Nexus podcast is to sign up for our newsletter? The Nexus Newsletter is your one stop shop for staying up to date on the latest smart building trends. Sign up today free of charge, and we'll drop this industry leading resource right into your inbox every Wednesday.
[00:00:39] If you're already signed up, double high five and thank you. But now tell your coworkers and your friends once you're signed up. The best way to continue the learning. Is to join the Nexus Pro membership community or our online course offering. Headlined by our flagship course, nexus Foundations. Diving into these products allows you to connect with our global community of like-minded change makers.
[00:00:59] [00:01:00] Licks are below in the show notes and now on the pod.
[00:01:08] All right, welcome to the Nexus Podcast. This is the first episode in a new series, diving into Case Studies of Real Life. Larger scale deployments of smart building technologies. I'm so excited about this. I emphasize the word real life because we're not really here to create some sort of marketing fluff story here.
[00:01:26] We're here to share real lessons from leaders that can, that have put smart building technology into their building programs. I also emphasize large scale because we're not here to talk about pilot projects. We're here to talk about. Deeper commitments to integrating technology into operations and sort of actually changing the way buildings are operated.
[00:01:46] So today we have a story coming out of the University of Iowa on their journey, integrating fall detection and diagnostics or f d d from here on out in this conversation, um, into their maintenance operations. [00:02:00] And so, Tom, we're gonna start with you. Can you introduce yourself and talk about your role on the team?
[00:02:05] Tom Moore: Tom Moore, senior Manager of Operations and Maintenance for the University of Iowa. Uh, my teams cover all of our education funded buildings on campus. Uh, that's basically classrooms and research and no sports, no hospital, none of that kind of stuff. The reason I'm on this team is it's very important for my team as a maintenance group to be able to go out and solve these problems efficiently and quickly instead of just tickets coming out from, from heaven and, and, uh, No one knowing where they're coming from.
[00:02:31] So that's why I'm mainly involved is because as the end user, the person, the group that's gonna have to fix these problems, we wanted to make sure we're a part of the process.
[00:02:40] James Dice: Absolutely. And why would you say, from the university standpoint, why do you guys use f d D? So what are the outcomes you're hoping to get from this technology?
[00:02:49] Tom Moore: FDD is a tool for our group. Uh, we have a group called the our group, uh, the an Analytic Resource Group. They're a little bit bigger than f d D, we're actually a lot bigger than F D D, uh, they're kind of our [00:03:00] retrocommissioning group, but they use f d D tool as a tool to. Find things, find which buildings we need to go to and take the best look at it along with, uh, deciding the day-to-day what needs to be fixed just without all this retrocommissioning blitz stuff that we do.
[00:03:15] So we do blitz with this group. It's basically we take this whole group, all the mechanics that work on the building, uh, upper management and everybody, and we go to this building and we're saying, we're gonna bring this building back up the snuff. We're gonna generate projects out of it. All that good stuff.
[00:03:29] So that's what's great about the F D D programming. It, it. A lot of that reporting stuff we already know. Uh, a lot of the root causes we can figure out pretty easy with what, what the tool does. We started out with wanting to see all this energy savings and we did see considerable energy savings, but now that we're probably five years in, we're definitely switching to, uh, Concentrating on a maintenance program as opposed with an energy benefit, as opposed to an energy program with a maintenance benefit.
[00:03:55] James Dice: Cool. Very cool. And from the maintenance side of things, I think, I think a lot of [00:04:00] listeners will be familiar with the benefits of energy savings. Obviously we don't need to dig into that. What are you looking for from a maintenance perspective? Like what, what does it, what does success look like from, from a maintenance perspective,
[00:04:13] Tom Moore: finding that needle in the haystack.
[00:04:15] Just takes you right to the needle and you don't have to worry about all the, the hay around it.
[00:04:19] James Dice: Got it. Yeah. So, so getting for the same amount of time, you're looking for issues, the software can help you get there faster.
[00:04:27] Tom Moore: It also helps our new technicians, uh, for with training, they actually get to see what a seasoned tech would look at on our faults.
[00:04:34] Uh, so they're not just starting from scratch either. They probably wouldn't have never been able to diagnose this problem without all the help that.
[00:04:42] James Dice: Totally. And just to set the context for the rest of this discussion, I'd love to just sort of rattle off a couple questions rapid fire round for you before we get into the details here.
[00:04:51] Who's the software vendor that you guys are using today?
[00:04:54] Tom Moore: We use Clockworks through our Schneider partner, the Base Point Group.
[00:04:57] James Dice: Cool. And how many buildings is, uh, the [00:05:00] software installed in?
[00:05:01] Tom Moore: Uh, 47 currently, uh, we've had up to 54. I think at one time I think about 10 buildings. We decided we weren't seeing the benefits, so, uh, we reduced and then added a few.
[00:05:09] But 47 is what we're currently staying at.
[00:05:13] James Dice: And what's the total square footage?
[00:05:14] Tom Moore: 6 million. 880,000.
[00:05:16] James Dice: And when did the project start?
[00:05:18] Tom Moore: 2014.
[00:05:20] James Dice: What sort of results, outcomes have you guys seen that you're measuring, uh, over that time?
[00:05:26] Tom Moore: You know, we use tasks to show what we've looked at and what we've closed out, and we've co closed out over 2100 tasks in that, which is a considerable amount stuff.
[00:05:36] Um, we've saved over two and a half million dollars proven dollars, not avoidable cost proven savings through our energy bill. So that's, that's how we're ging our success.
[00:05:45] James Dice: Awesome. And. Before we bring, we have a few more friends here before we bring them on, can you talk about the deployment and sort of integrating the software into the operations?
[00:05:57] Tom Moore: Sure. Um, we started out, [00:06:00] as a lot of people do, we thought we could self-manage, you know, nobody's better than us. And, uh, And doing maintenance stuff. So we wanted to bring everything in house. We were gonna have it on-prem. We were gonna make our own faults, we were gonna make our own graphics, uh, we were gonna do all this stuff Since we were a partner with, with Microsoft, we went with an icons platform, uh, which is a.
[00:06:20] Does exactly what it's supposed to do. Uh, but it just didn't fit us. After that first year, we were spending way too much time building our own graphics, doing all that stuff that we realized why not have this team of people from all around the world developing the program for us. So we went out for an rfp and that's how we got hooked up with Clockworks.
[00:06:40] Uh, once they got on board, that's when things really, really started to ramp up in my opinion. As far as seeing savings and different things like that, we decided to do a pilot. 10 buildings, a mixture, not necessarily who we're gonna save the most money on, but we wanted classrooms. Uh, we wanted inner energy buildings, so like research labs, some [00:07:00] of the athletic facilities, uh, amounts of equipment, uh, high and low.
[00:07:04] We wanted to try all those so we can, you know, base what we would move forward with if this was successful. Uh, so it was very successful. So we went with a round two. I believe we did 23 more buildings in round two. Uh, we did a lot better selection then. Uh, it wasn't so much we're trying to discover. We already figured that out during that first pilot.
[00:07:23] Um, so I think the first pilot, they onboarded us in about three months. The second one, I think took a little bit longer, more like eight months to get the second one onboarded, which is understandable. There's much more, um, Work to do there. Um, I will say in their defense, I was telling him to slow down.
[00:07:40] How am I gonna do all these buildings checked out and everything else? So what I was saying, you guys gotta slow down. You gotta slow down. Which, um, I'll never say again, but it was amazing how quickly they onboarded it, where we just spent a year doing one building. You know, they brought on 43 buildings in less than 11 months.
[00:07:56] But once we had all that, that going, we decided to form this, our [00:08:00] group A, we got about 3,500 faults we could be acting on. So, We got plenty of things to do every day.
[00:08:06] James Dice: Yeah, I love that story because it shows the journey you went on one software provider, it didn't quite work for us. Thought we could do a lot more in-house than we, than we actually could.
[00:08:16] So we pivoted, went out for rfp, did another pilot, and then rolled out in a large way and then built the team, developed the processes. Um, so we're gonna focus on those two things. Last things. We're not gonna go into why you selected a certain software. Today we're gonna talk about the team and the processes, and the idea here is to dive into those two things because it really, I think that's where we're at sort of as an industry is that I think a lot of people have validated that this tool is needed.
[00:08:45] Especially when you have more buildings than your operations folks can get a grasp on, right? You have a lot of deferred maintenance, you have stuff breaking all the time, you have a lot of hot and cold calls. People have realized that f d D is an important tool, but I don't think a [00:09:00] lot of people have figured out how to integrate it into their team and, and, and make it work on a day-to-day basis.
[00:09:06] So now let's bring in Brad and Katie. They've been ghosting in the background here, and then they're gonna bring him onto the front stage. So Brad, let's start with you. Can you, uh, do a little introduction to yourself and talk about what your role is on the team?
[00:09:20] Brad Dameron: Yeah. I'm Brad Damron. Been at the university now for almost four years, and I was kind of brought in to.
[00:09:28] I think try to take the FTD to the next level and really branch out. You know, initially when they got the software, you know, it's, you get a lot of the low-hanging fruit. Oh. You get these big projects and big savings and those are pretty easy to pick and choose from. And you know, it's gets people excited.
[00:09:46] But then after you've had it for a while, okay, the savings kind of goes down and down if you're doing your job. So, okay, now what do we do with it? Well, we need to refocus and, okay, how do we use this as a maintenance [00:10:00] software and how do we be more proactive rather than just, okay, it's finding these things.
[00:10:06] Okay, what are we gonna find before it becomes a big problem? That's kind of the more of the push, and that's where. More of my role, I guess, is, you know, trying to be that more proactive person. We're looking for these things that we can catch before they become a big problem, and then actually getting it out to the field, getting it out to as many people as possible so we can get as much done using the software as we can and just trying to be more efficient.
[00:10:33] James Dice: Cool. And we're gonna come back to a lot of those process oriented things that you're sort of delegating tasks out and that kind of thing. Katie, can you jump in and introduce yourself, uh, and talk about your, your role on the team?
[00:10:46] Katie Rossmann: I'm Katie Rossman. I, uh, was on the team with Tom that helped to, um, implement the F D V program at the University of Iowa.
[00:10:55] I sort of had a dual hat of energy engineer when I first started the program, [00:11:00] and then I moved into more of a. Leadership role as the, uh, manager of building analytics and commissioning, but I still really wore that energy hat as part of a member of the, the ARG group. I have now since transitioned from my position at the University of Iowa and I work actually on the Clockworks Analytics side.
[00:11:18] I've been there for about two years. I am, uh, the director of the Technical Operations Center, uh, which I lead up the team of service engineers that help clients like the University of Iowa with. Process improvement, uh, helping them use the tool, find value out of the tool. So I basically would do the same thing that I did at the University of Iowa, but for a broader audience at Clockworks.
[00:11:41] James Dice: Yeah, so you can weigh in on how you guys did it at Iowa when you were there. You can also weigh in on best practices that you've seen since you've left, uh, in terms of people integrating the technology into operations. Absolutely. Can you guys, starting with Scott, talk about the other people on the team and what their, sort of, what their other roles are.
[00:11:59] All [00:12:00] of these people aren't here, so we won't drag their name through the mud at all, but, uh, talk about what they're doing on the team.
[00:12:07] Tom Moore: So Scott Soner is our controls technician, controls lead as part of our group here. He's really involved with the programming side of stuff. He'll definitely go out in the field and, and help with that stuff, but with this platform you do find a lot of programming changes that you need to have.
[00:12:21] So he's, he's responsible for either making himself or getting it to the other people. On the controls group that we have here at Iowa, we're very. Very lucky at Iowa to have a controls group, as I think it's up to eight people now, uh, that Jude does think nothing but programming and, and and BS work.
[00:12:37] James Dice: Awesome. And, and who else would you guys consider to be on the, the core team?
[00:12:42] Tom Moore: An IT professional for sure. Ours have to be guy named Sarm, but, uh, without the IT professional, I don't think we, we would be where we're, where we're at for sure.
[00:12:51] James Dice: Totally. And, and do you, can you just talk about a little bit in more detail of what, what his role is on the team?
[00:12:59] Tom Moore: Yeah, so [00:13:00] during our RFP he was very integral. Um, he was telling us what, what was real, what wasn't, what these vendors were telling us. He was telling us how who we could integrate and who we couldn't integrate with. Uh, it wasn't us making a decision and going to it and telling him to make it work. It, uh, he was really, really important, uh, to make sure as part of the selection committee, um, On what we were gonna choose.
[00:13:22] So then once that happens, he runs all the background stuff, make sure the connections are there, the firewalls up, and doing all that good stuff. He also, he tells us when we need to change our, I mean, literally some of our, our programming stuff, he's, he's helped out with. So, but definitely in the beginning, that role gets really diminished after you get rolling.
[00:13:42] But in the beginning, you have to have it, or, or you're just, you're gonna be wasting a bunch of time. Because you're gonna pick something, you're gonna take it back to your IT professional and they're gonna say, we can't make that work. So now we gotta go to number two. Had we had him on the first, uh, pilot, more involved, I think we would've probably made some different [00:14:00] decisions, uh, which, so that we definitely made in the second pilot.
[00:14:04] James Dice: Got it. Okay. All right. Who else on the team?
[00:14:10] Tom Moore: I would say all of our, all of our frontline techs and our managers, were really trying to integrate them much more than we had in the past. So I would say that they're, they're definitely part of our team.
[00:14:19] James Dice: Got it. So it's not just this, this external team that's sort of throwing stuff at the frontline technicians.
[00:14:26] It's Right. These people are part of the team and we're sort of trying to integrate it into their, their daily workflow. Yeah. That's awesome. Yeah. So. I understand with this team, when you guys were building it, Katie, there was something that you were arguing maybe with Tom about that
[00:14:43] Katie Rossmann: friendly banter.
[00:14:43] James Dice: In retrospect.
[00:14:44] Katie Rossmann: Friendly banter.
[00:14:45] Tom Moore: Friendly banter. There you go. There was no arguing.
[00:14:48] James Dice: In retrospect, it looks like you're on, you're on Tom's side now. Can you talk about, uh, that sort of friendly banter argument?
[00:14:56] Katie Rossmann: Yes. So to be clear, Tom and I are very much peers as [00:15:00] we were sort of given our. Our charge to go figure out what this F d, D thing is.
[00:15:05] And we had talked to some other folks who had been using the tool. It had been sort of sold to us as an energy tool. And so, you know, my thinking was instantly like, this is an energy management functionality. This is something that energy managers take. We look for problems and we communicate it like in a more classic.
[00:15:25] Energy conservation measure, energy project, spreadsheet, you know what I mean? And track it outside of, of your maintenance organization. And Tom kept pushing me like, no, Katie, this needs to be something that maintenance does. Maintenance needs to have a really integral role in this tool. And, um, and I, I, it was very much a difficult mindset for me to grasp that.
[00:15:47] Um, it can't be the more. Kind of rigid, uh, project implementation that needed to be part of our day-to-day lives and how we do maintenance. And so, um, I will never live it down, but Tom was a hundred percent [00:16:00] right and I was wrong. That I really believe that was integral to our success is the, the integration to our c m s, the, um, the use of work orders to push action instead of relying on some external tool that are, um, are.
[00:16:16] Our maintenance people don't speak tasks. They speak work orders. And so the more it looks like their day-to-day hot and cold call, the better it is, right? So if we can make that push of that F D D resolution look like a work order, then it's much easier for the organization to adopt it. And also they get.
[00:16:36] Much better adoption when it's someone like Brad who's sending the work order out, who can go and get his hands dirty and fix the problem. And you know, if they need help, he can go help them. Whereas if it had been me sitting at my desk looking at energy numbers in a spreadsheet, I don't think there would've been that same buy-in.
[00:16:53] So I think that was really important that we had well respected, um, really good technicians that [00:17:00] were already fixing broken stuff anyway, just come and fix it in a different way.
[00:17:06] James Dice: I love this insight because you know, in a lot of organizations, an energy engineer could be an external consultant. It could be someone in a different department, it could be someone on the portfolio level that's kind of outside of the, the group.
[00:17:18] They're not boots on the ground, they're not there every day fixing stuff, right? So the fact that you guys decided, well, Tom overruled you there and decided didn't.
[00:17:27] Katie Rossmann: No, no, no. It very bad. No other. It was
[00:17:30] Tom Moore: very fun. Finally, her truth,
[00:17:40] the cmms. This is, we treat these like any other work order. They do not get special treatment when it goes out to the frontline. And I should have said that earlier. So that also helps with the implementation too, because we have what our customer timeframe expect expectations of when tickets are gonna be finished.
[00:17:55] Uh, so we are able to use that metric to see how successful we were being with these [00:18:00] frontline folks.
[00:18:01] James Dice: Totally.
[00:18:02] Katie Rossmann: I do think this actually really speaks to the same decision we came to with our, what platform we used was what our organization was good at. I've seen this energy management run F D D programs work well at other organizations, but with the resources we had at Iowa, the funding sources we had at Iowa.
[00:18:22] The levers we had to pull to execute work. If it wasn't gonna work, if it was coming through as an energy project, just based on history at the university and, and the resources that we had at the time, it was going to be a much more successful program if it was run through our maintenance organization and we had such good buy-in from leadership with Tom that like, you know, that helped a lot too, right?
[00:18:43] That, that we were both at the table together as peers kind of coming up with what this program looked like. I think that was also really helpful in, in our success. And we do obviously like still like each other, so it must have worked.
[00:18:56] James Dice: Yeah.
[00:18:58] Tom Moore: School.[00:19:00]
[00:19:04] James Dice: So before we move on to the actual process, um, Which is one of the things I'm most excited about here to talk about the big ass flow chart. Um, Tom, I wanna see if you have any advice for people that are trying to select who should I make this analytics super user on my team? Should it be the top technicians?
[00:19:22] I think a lot of people say, no, I want my top technicians out there still doing what they were doing before. They're the most productive people. I think they say. Maybe I'll. You know, pluck this newcomer and, and have them be the person. Why, why did you guys select the top technicians?
[00:19:39] Tom Moore: Because the, they're still doing work, right?
[00:19:41] I mean, this is not like we, you know, drug the work system down in the shop once they left because they were still doing stuff in that shop. Uh, but it may not not be all day. Right. And, Really as good stewards for the university, we need to put the best people in every best situation that fits that situation the best.
[00:19:59] [00:20:00] We're distributed. We're not a central, uh, maintenance group. We have five shops on campus. Um, it's great to have these, this group just be that single point of truth, right? Like, if I have a problem, I'm gonna call them, this is what I'm looking for, this, you know, they're watching my back with this program because they might be able to get something fixed beforehand.
[00:20:20] Getting projects done that never would've got done before, right? Because without we have the, the data and the proof to say, Hey, this is, you know, we need to do this. We we're, we could be saving, you know, $25,000 a year just by, you know, getting this air handler outta here. Uh, selfishly I knew I needed some people that were well respected on campus, you know, known to be teachers with others, and known to get the job done, helped out
[00:20:41] Katie Rossmann: and, and they, they were doing F D D.
[00:20:44] On their own anyway, right? So they were already manually looking at the b a s in the morning to try to find problems. So it's just replacing the tool was something that's easier for them.
[00:20:54] James Dice: Absolutely. All right, let's talk about the big ass flow chart. I, I first saw this, uh, last [00:21:00] fall when I was with you, you all in Boston, uh, which was super fun.
[00:21:04] I was very impressed by the detail in which you're laying out this like process flow. Um, Brad, do you wanna take us through, describe what this is? We'll, we'll put a link to it in the show notes. We'll, we'll share it like this actual flow chart with everyone that's listening to this. You can find it on our website.
[00:21:22] Um, but Brad, can you talk us through it?
[00:21:25] Brad Dameron: Yeah, yeah. This is actually, uh, One of the first things I helped with when I started here is we said, you know, we really need a flow chart so we can explain well, both to ourselves and everyone else, what does it look like when a fault comes in? What are our duties?
[00:21:42] And yeah, the number one thing is, uh, you know, is it a true analytic? You know, people think, well, yeah, it just spit it out to us and we just automatically put out a work order or something. First is evaluate, is this. Is what this is telling me true? [00:22:00] Is it a sensor error? Is it a, you know, is it a mechanical thing or does this not make sense at all?
[00:22:06] I mean, you know, not every fault is a real issue. And so gathering all that information with the software, we get all the trends and we can see all the sensors that are involved, how they decided that this was an issue. And oh, you still gotta put a human brain to it at some point and say, okay, does this make sense?
[00:22:28] If it doesn't make sense to us, we have regular meetings with the software provider that we can take issues to. It's like, you know what? This doesn't make sense to us. We don't think this is a true fall, or, oh, can we adjust this fall? You know, this is too tight a tolerance. We've had to do that many times.
[00:22:47] You know, Brian and I are the first line of defense, so we're looking at these faults day in and day out. We both have over 25 years experience in HVAC and controls. So between the two of us 50 years experience, [00:23:00] we can kind of tell, okay, you know, I got a pretty good idea what this is. Then I can say, I can either send it to the group area maintenance guys and say, well, I want you to look at this.
[00:23:11] I'm pretty sure this is the issue, and if it's not that, then go ahead and get back to me. That's the ideal situation. So you know what? This is kind of a bigger scale thing. Then we'll go out ourselves and put our eyes on it, you know, put meters to it and verify, okay, this is a issue. Okay, we know exactly now what trade we need to get in there.
[00:23:36] Okay, we need electrician, or we need a pipe pitter to change out a valve. This valve is failed. Um, or is it an electrical issue or. You know what? This is even bigger scale. We need to create a project cuz we have around 3,500 faults per day that we're trying to prioritize. And the software does try and bring up the top scoring faults.
[00:23:59] [00:24:00] So this is where we show the most money it's costing you. Or we can sort by comfort issues. This is what's causing the biggest comfort issues that you might wanna address. Or we can sort by maintenance issues. Okay, this is a mechanical failure. The top mechanical failures that we've, you know, come across and we kind of have different focuses on different days or even maybe even weeks or months.
[00:24:25] It's, that's where I think it takes somebody that has that experience and can decipher what direction you're going with that. Also, we figured out that the software actually provides a link. To all the trends and all the data that it used to find that fault. We attach that right to the work order so the tech out in the field can just click on it now and go right to the fault.
[00:24:50] And they've really been loving that too. And you get a lot more buy in that way. It's something we've learned that that that goes a long way.
[00:24:58] James Dice: Yeah, sure. I'm [00:25:00] sure. Thanks for taking us through that, Katie. I'm wondering, so one of the things I think is interesting here is we have the integration of two systems, right?
[00:25:07] We have F D, D, and we have a work order system or a cmms. Those two pieces of software are integrated with each other, but it doesn't seem like that integration is automatic, really. It's not like every fault is coming in and creating a work order. So, Katie or Brad, however you guys want to take this, but can you talk about, um, why.
[00:25:29] It's only some of them, and maybe it's obvious, but I think it's not obvious for the the tech folks that are just like integrating everything together. Right. Why is that a manual decision of what gets brought in from the F D D to the work order system?
[00:25:44] Katie Rossmann: I think the main reason that it is a manual process.
[00:25:47] Is, um, because of what Brad was speaking about, about that kind of pre-vetting of the diagnostic results, your output is only gonna be as good as the data it's consuming. So sometimes you'll have issues with sensors that are causing [00:26:00] problems, you'll have issues with. The way that diagnostic might be configured is, is based upon a sequence of operations that no longer is used anymore, or it's based upon assumptions that Iowa no longer.
[00:26:13] It makes anymore. Right? So having the human input of generating that work order gives it just kind of that first bet before you send it out to the field to go look at it. You're doing that, that kind of initial triage to say, um, okay, here's where the issue is. The other reason that it's nice is, is because a lot of times what you're looking at potentially are.
[00:26:35] A list of symptoms and then a problem, right? And being able to see all of those symptoms in tandem with the problem allows you to kind of say, okay, the root cause of this issue is this one valve. So it also allows you to kind of send that work order out and say, pay attention to this valve. There's all of these other symptoms that are happening, but the thing that you need to fix is the valve.
[00:26:55] So it does kind of allow you to, to like when you're actually taking action, give [00:27:00] directed information to the field. Right. And, and when you're getting that diagnostic result, so kind of to Brad's point, you're seeing all of those symptoms and the problem identified for you, right? And you're seeing like a list of recommended corrected actions.
[00:27:14] When you create that, that work order, um, it's gonna show all of those things together, right? Because they're kind of, they're all interrelated. And so if that were to automatically send out. It might give, you know, confusing instructions to the technician too. So Brad's able to say, okay, I see all of this information at once.
[00:27:34] This is the problem. And kind of narrow down on that.
[00:27:39] James Dice: Amazing. So I, I want to kind of repeat sort of the, the big S flow chart, sort of back to you guys. There's one loop of, uh, an ongoing meeting and tasks around just making sure the software is doing what it's supposed to be due is, is keeping updated, is um, Sort of tailored to how you guys wanna see it.
[00:27:59] And then there's another [00:28:00] loop around tasks and validating tasks, tracking tasks, getting them implemented. So that's an ongoing meeting. Repetitive meeting as well. And then there's this triage piece that Brad and Brian are two sort of super users are saying. I'm gonna assign this to the right trade. I'm gonna track this, I'm gonna support them in the implementation, and then I'm gonna see if it's resolved after the fact.
[00:28:24] And so it's like kind of like three different loops going on. That's really cool. That's really awesome. So let's do a little storytelling. Is there one project that comes to mind, Tom, that you would tell to another university at a conference saying, lemme tell you this cool story about what we did in our F D D program?
[00:28:45] Tom Moore: So this is one when we, with the original software and when we first started doing this, right? So, uh, this one was kind of my aha moment. It does work. Uh uh, so we just built a new huge wet lab building, a biomedical research building, a [00:29:00] six stories of wet labs, and then another 40. Feet or poor stories in the ground with supporting equipment and oar space and different things like that.
[00:29:07] So, uh, this was the building we picked to do first had to pick the most complicated building we had, newest building we had on campus, which I think is great cuz we learned a lot by doing that as opposed to if we just had a couple quick wins we would've never made in the decisions we made. So, um, the guys found out that they were not getting the discharge air temperature that they thought they should out of a va out of a bunch of VAVs in the scene.
[00:29:31] Same room, right? So they go out there, they start setting up their ladders, and the department head comes home and goes, what are you guys doing in here? And they're like, well, we've, we've run the software over here, over our building automation system that's telling us that you're not getting the heat that you need to get out of these coils.
[00:29:49] And they're like, well, it's fine to us, but if you wanna go ahead and check it out. So Jeff and Bob get up there and we had to have the pipes reins insulated as part of one of our. Punch alerts, checks for this [00:30:00] building. Insulator came through, insulated and shut all the hand supply and, and returned hand battles off to all the VAVs.
[00:30:06] So we had no hot water going to those VAs. So Jeff and Bob went up there, opened the ball up, and the, you should, it was like, They almost applauded 'em as they left. They're like, this is the best it's felt since we've been here. And they're like, well, why didn't you call us? And they're, they said, well, it's a new building.
[00:30:21] We just assumed this is what we were gonna get. I just thought it was supposed to be like this. Yeah. So win different levels. We had win with the customer, win with Software Works. We're. We really got into this hoping we could do predictive maintenance. Right. Um, you know, with some of the AI stuff that's coming out and different things.
[00:30:39] So that to me was about as predictive as you can get. Right. We, we, we solved the problem before it became a problem and it was a problem, but, uh, the customer didn't know they had a problem.
[00:30:49] James Dice: Yeah. So the, the output on the valve was, I need heat. Right. But then you had a manual valve those closed down not letting it get any water.
[00:30:56] Correct. And, and, I guess, how long would it take to [00:31:00] find something like that? You wouldn't find it until it's the coldest day of the year or something. And yeah,
[00:31:04] Tom Moore: till, till they complained, to be honest. Yeah.
[00:31:07] James Dice: Yes. So the last 10 minutes we have here, I, I would love to talk about some lessons learned here and we've kind of gone through these together before we, we hit record here.
[00:31:17] So I'm gonna sort of feed them to you guys and then I want you guys to sort of talk about those. So the first one, and I think this is my near and dear up to my heart, because it sounds like there was some pushback from technicians that were saying like, You know, this, all this analysis that this software is doing, that's, that's my stuff.
[00:31:36] That's my magic. That's where, that's my career that you're sort of automating away. Um, how have you guys sort of managed that, that piece of this, because obviously on one hand we're using technology to. Get more out of less people. But on the other hand, if someone really likes trying to go find problems and finding the needle in the haystack manually, [00:32:00] you might upset them.
[00:32:02] Brad Dameron: It is still an issue for some people and it's, it's showing them that, you know, most of the things that these, that the software finds. Is not things that you're gonna find just stumbling across it. You know, if you're sitting there looking at your b a s all day, every day, yeah, you're gonna catch it, but you have work to do and it's convincing then that we're not there looking over your shoulder.
[00:32:29] We're not trying to make you look bad, we're trying to, we're there to help. You know, this software is helping you do your job better and it's. Finding the needle in the haystack. It's not something you're probably going to find. You know, those things are reactive. You know, we're not looking for the reactive stuff.
[00:32:47] We're trying to find it before it becomes a, a big deal. And it's just, it's, it's educational. It's just getting out there, talking to the people, showing them what it's all about, and showing [00:33:00] them that we're not here to make you look bad. It's not going to make you look bad. It's, you know, it's just another tool.
[00:33:06] In the toolbox and that's what we, we really try to emphasize. This is a tool that we're using just like all your other tools.
[00:33:15] Tom Moore: They take pride in when we have a $25,000 energy save. They're involved. They're helping with that fix. Having those kind of winning situations really helps. It also helps we, we spur projects that improve their space.
[00:33:28] Right that we weren't getting money for before. So I think through several projects that we had done through our Im u Blitz and, and different things, and we made the building that they take care of so much better, they see the benefit of this. Right? So it's kinda
[00:33:41] going,
[00:33:42] Brad Dameron: we actually, yeah, we talk about, you know, peeling the onion.
[00:33:46] This fall may start pretty small and the energy savings on this fault may only be a few dollars. By the time you unpack that and you keep peeling the onion back and peeling it back and peeling it back, this thing just gets grows and grows and grows and it's like, you [00:34:00] know what? This is actually a big deal.
[00:34:02] We can submit this as an energy project. And I mean, we've had some big success stories.
[00:34:08] James Dice: Totally. Okay. The next one we had was evaluating where your strengths are. It sounds like you guys talked about this a little earlier. There was a little bit of like biting off more than you could chew at the beginning.
[00:34:20] So how have you figured out as an organization there's a lot to do here? IT software, programming database. Um, Obviously all of the implementation we've been talking about, there's a ton to do in this process. How have you decided what to take on, what to outsource, et cetera?
[00:34:40] Katie Rossmann: So when we initially did our pilot and we were looking to self perform everything, I think like one of the biggest data points that proves that there's a.
[00:34:51] Something to be said for letting someone else do something that's better at it. And that's the onboarding time. So when we onboarded that one building and our [00:35:00] pilot and we did all of the self-performing, it came down to, I think it took us six months. To just get points communicating felt like just the learning curve of figuring out the integration and how to point map everything in, and then writing faults and the management of those faults, right?
[00:35:17] The change management of, oh this, this air handler operates this way, this one operates slightly different. And like trying to track all of those changes. We just didn't have the tools, the resources, the people to manage all of that. It was basically just going through me to make any adjustments to the analytic results.
[00:35:36] And, and so I think that alone was sort of like, we probably shouldn't do this in a vacuum. Right? There's a, there's a beauty to being able to crowdsource some of this stuff that people have already. The case I really made, and I was like, I think we need to pivot here, was. There are people all over the United States writing the same economizer fault 10 different ways.
[00:35:55] Right. You know, it's like, why am I the 11th? You know, so I, it just, it feels like [00:36:00] there was some, some like scalability that could happen through kind of a crowdsource model. So that's one of the main things right away that we were like, this is not something that we can take on as an organization. That's not our strength.
[00:36:11] We have always been very particular that the troubleshooting and determination that something is. Is actionable. We have owned and that's remained, that's been the, like our bread and butter. And that was really from the very beginning was we wanna own deciding what we do in our organization as far as what tasks and work orders we say are actionable, right?
[00:36:33] Because we understand our business model, we understand the, our priorities and what's important to us. So that was something we always really wanted to own.
[00:36:42] James Dice: And this is a thing that, you know, you guys have seen a couple different f d D vendors. I've seen like all of them. And, um, it's important for people that are listening to this, that are just starting down this journey.
[00:36:53] Not all f d D products can do what Katie just said in terms of crowdsourcing and sharing these [00:37:00] concepts across customers, across buildings, across geographies, across. Units like in, in Europe or Asia or whatever. And so one of the things we're trying to do with our partner program is really set standards for, if you're selecting F D D, it needs to be able to do this.
[00:37:16] And I think that's one of the things that's really important, is being able to use what other people have already written. The other 10 people that are writing economizer rules, the the product should be able to make it so that we're not recreating the wheel. Every time. The third lesson learned you guys gave was having leadership buy-in from the beginning.
[00:37:36] Could you guys just tell that story of how this kind of started with Don and his sort of vision that sort of helped you guys get this off the ground? I.
[00:37:45] Katie Rossmann: Don gk, who was the AVP at the time at Iowa, came to Tom and I and said, you know, I've read this article, uh, this Doug Tweer also was, was pretty instrumental in this.
[00:37:56] And there was an article that had been written about Microsoft's [00:38:00] implementation of F D D. It probably was from like 2008 because this, that's when this journey really started. So I think even pre, pre, Tom and I, you know, Iowa had made a trip out to Microsoft, had had visited their campus, had seen their F D D program in.
[00:38:14] In life and then came back and kind of told Tom and I to, to make it work, right. So then we, we also took a trip out there and we, we talked to the people that were making their F d D program work, so we kind of asked some questions about it as we were implementing our pilot. But from the very beginning, Don was a, a very good champion for our program and one of the biggest lessons that he taught, To like very nervous people about something going wrong is to not be afraid of failure.
[00:38:41] Right? So, so keep going, right? And take some of those risks. And if it fails, we can always change course. And that was really important guidance for us as we were looking for more like, why are we doing this? Are we wasting time? And he just kept pushing us to just, just test the limits and the boundaries, see what could work.[00:39:00]
[00:39:00] And when we made this decision, we went out for RFP and the decision was sort of like, This vendor we're picking is not the one that we've spent all this time and resources on. Is that a negative here? And it was just sort of like, that was a a year of learning and we need to pivot if it's the better option for us going forward.
[00:39:18] And um, it made that choice a lot easier for us to, to make that switch because so much time had been invested in that initial pilot.
[00:39:27] Tom Moore: And that went all the way up through the president's office. He did a great job. He sold it to them too. But I ran into him in the hallway about six months after he started, and he's asking me how it's going, and I was listing off stuff that wasn't working and he goes, I want you to stop right now.
[00:39:41] From now on. I only want to hear what's working. I don't want to hear what's not working. It's your job to figure out why it isn't working, not mine. So I only want to hear the good things, you know? So that was one thing that was like, he was basically saying to me, I don't care if you screw up Tom, I'm never gonna know about it.
[00:39:55] Even if I do, I know it's part of the process. You know, 10,000 tries to get a light bulb. [00:40:00] Uh, so I, that helped me out. Tremendously.
[00:40:02] James Dice: Yeah. So somebody that understands that this is a, a process that we're learning here. We're adopting something new, there's a lot of change management involved and and can kind of roll with the punches a little bit.
[00:40:13] That's awesome. So I wanna thank you guys so much. This has been super in insightful. I think a lot of people will learn a lot, I think. That original Microsoft f d d article was one of the reasons that I kind of went down the path that I went on. It's a, it's an inspiration still because think about all the people that have gone down the path since they read that.
[00:40:32] I'm hoping that when people listen to this, they can kind of have a, a similar light bulb. Come on. So before we close this out, I want ask each of you anything that we've missed that you wanna quickly say before we close off.
[00:40:47] Tom Moore: Just having the right team is a big deal. You gotta have the right players.
[00:40:50] We're successful because we picked, like, got lucky and picked the right players and you know, we're okay with failure. You're gonna fail cause you can't, you [00:41:00] know, all those lessons were learning lessons for us. Right. We wouldn't be where we're at without that first program. We knew what we wanted after that.
[00:41:05] We knew what we needed.
[00:41:08] James Dice: Yeah, totally. Katie, Brad, any any closing insights?
[00:41:11] Katie Rossmann: I will actually echo this. This team team strength I think was also really important to our success. I loved this program. I could talk about it all day long until I'm blue in the face. It's not just, we're not just, I. Advertising for the University of Iowa truly was a real joy to work with this team, and I think the thing that I liked the most about it was that it was truly results driven, right?
[00:41:34] You can't hide behind fake numbers because people will, Notice when your bills don't go down, or when work orders don't get closed, or when your numbers never move, right? There are results that you can tie to your success. And so it was a really, a really meaningful part of my career as being able to work on a team to, to implement a program that has lasted so long, um, at a big institution.
[00:41:58] James Dice: Awesome. How about you, Brad? [00:42:00]
[00:42:00] Brad Dameron: Yeah, I mean, I would echo, you know, having that team of people that are results driven. I think cuz that's, it's very easy to see your results here and that's something that I'm driven by. You know, I wanna see results from my work and you get instant feedback. Now the only other thing I would add is, You know, the educational as aspect, oh, from the top to the bottom.
[00:42:23] That's one of the hurdles. I mean, it's just educating people from the top to the bottom. This is a tool and this is how it gets used, and these are the benefits and it's, it's constant, you know, we're how many years in and we're still, you know, educating people and it's, it's just going to take time and, and education and that was the only other thing I wanted to add.
[00:42:45] James Dice: All right. Thanks so much for, for coming to, to, to share your story here. This is a great story and I think all people are gonna get a lot out of it. So thank you so much.
[00:42:56] Rosy Khalife: Okay, friends, as we're trying these new formats, please [00:43:00] let us know what you think in your podcast player right now, or on the episode page on our website. There's a link to a survey for this specific episode. We'd love to hear from you and we wanna hear your feedback. Also, don't forget to sign up for the Nexus newsletter. Or invite your coworkers and friends with a link below.
[00:43:17] Catch you next time.
"Maintenance needs to have a really integral role in this tool. And so the more it looks like their day-to-day hot and cold call, the better it is, right? So if we can make that push of that FDD resolution look like a work order, then it's much easier for the organization to adopt it. And I really believe that was integral to our success."
—Katie Rossmann
Welcome to Nexus, a newsletter and podcast for smart people applying smart building technology—hosted by James Dice. If you’re new to Nexus, you might want to start here.
The Nexus podcast (Apple | Spotify | YouTube | Other apps) is our chance to explore and learn with the brightest in our industry—together. The project is directly funded by listeners like you who have joined the Nexus Pro membership community.
You can join Nexus Pro to get a weekly-ish deep dive, access to the Nexus Vendor Landscape, and invites to exclusive events with a community of smart buildings nerds.
Episode 144 is a conversation with Tom Moore and Brad Dameron from The University of Iowa and Katie Rossmann of Clockworks Analytics.
Episode 144 is the first episode in a new series diving into case studies of real life, large scale deployments of smart building technologies. For this first episode, we talk with the University of Iowa regarding their integration of FDD via Clockworks Analytics. This project started in 2014 and includes 6.8 million square feet across 47 buildings. We hear the project team, the rollout, and key inclusion of their maintenance operations from the ground up.
Music credits: There Is A Reality by Common Tiger—licensed under an Music Vine Limited Pro Standard License ID: S441934-15083.
Note: transcript was created using an imperfect machine learning tool and lightly edited by a human (so you can get the gist). Please forgive errors!
[00:00:00] Katie Rossmann: Maintenance needs to have a really integral role in this tool. And so the more it looks like their day-to-day hot and cold call, the better it is, right? So if we can make that push of that. F D D resolution look like a work order, then it's much easier for the organization to adopt it. And I really believe that was integral to our success.
[00:00:24] James Dice: Hey friends, did you know the best way to continue learning beyond the Nexus podcast is to sign up for our newsletter? The Nexus Newsletter is your one stop shop for staying up to date on the latest smart building trends. Sign up today free of charge, and we'll drop this industry leading resource right into your inbox every Wednesday.
[00:00:39] If you're already signed up, double high five and thank you. But now tell your coworkers and your friends once you're signed up. The best way to continue the learning. Is to join the Nexus Pro membership community or our online course offering. Headlined by our flagship course, nexus Foundations. Diving into these products allows you to connect with our global community of like-minded change makers.
[00:00:59] [00:01:00] Licks are below in the show notes and now on the pod.
[00:01:08] All right, welcome to the Nexus Podcast. This is the first episode in a new series, diving into Case Studies of Real Life. Larger scale deployments of smart building technologies. I'm so excited about this. I emphasize the word real life because we're not really here to create some sort of marketing fluff story here.
[00:01:26] We're here to share real lessons from leaders that can, that have put smart building technology into their building programs. I also emphasize large scale because we're not here to talk about pilot projects. We're here to talk about. Deeper commitments to integrating technology into operations and sort of actually changing the way buildings are operated.
[00:01:46] So today we have a story coming out of the University of Iowa on their journey, integrating fall detection and diagnostics or f d d from here on out in this conversation, um, into their maintenance operations. [00:02:00] And so, Tom, we're gonna start with you. Can you introduce yourself and talk about your role on the team?
[00:02:05] Tom Moore: Tom Moore, senior Manager of Operations and Maintenance for the University of Iowa. Uh, my teams cover all of our education funded buildings on campus. Uh, that's basically classrooms and research and no sports, no hospital, none of that kind of stuff. The reason I'm on this team is it's very important for my team as a maintenance group to be able to go out and solve these problems efficiently and quickly instead of just tickets coming out from, from heaven and, and, uh, No one knowing where they're coming from.
[00:02:31] So that's why I'm mainly involved is because as the end user, the person, the group that's gonna have to fix these problems, we wanted to make sure we're a part of the process.
[00:02:40] James Dice: Absolutely. And why would you say, from the university standpoint, why do you guys use f d D? So what are the outcomes you're hoping to get from this technology?
[00:02:49] Tom Moore: FDD is a tool for our group. Uh, we have a group called the our group, uh, the an Analytic Resource Group. They're a little bit bigger than f d D, we're actually a lot bigger than F D D, uh, they're kind of our [00:03:00] retrocommissioning group, but they use f d D tool as a tool to. Find things, find which buildings we need to go to and take the best look at it along with, uh, deciding the day-to-day what needs to be fixed just without all this retrocommissioning blitz stuff that we do.
[00:03:15] So we do blitz with this group. It's basically we take this whole group, all the mechanics that work on the building, uh, upper management and everybody, and we go to this building and we're saying, we're gonna bring this building back up the snuff. We're gonna generate projects out of it. All that good stuff.
[00:03:29] So that's what's great about the F D D programming. It, it. A lot of that reporting stuff we already know. Uh, a lot of the root causes we can figure out pretty easy with what, what the tool does. We started out with wanting to see all this energy savings and we did see considerable energy savings, but now that we're probably five years in, we're definitely switching to, uh, Concentrating on a maintenance program as opposed with an energy benefit, as opposed to an energy program with a maintenance benefit.
[00:03:55] James Dice: Cool. Very cool. And from the maintenance side of things, I think, I think a lot of [00:04:00] listeners will be familiar with the benefits of energy savings. Obviously we don't need to dig into that. What are you looking for from a maintenance perspective? Like what, what does it, what does success look like from, from a maintenance perspective,
[00:04:13] Tom Moore: finding that needle in the haystack.
[00:04:15] Just takes you right to the needle and you don't have to worry about all the, the hay around it.
[00:04:19] James Dice: Got it. Yeah. So, so getting for the same amount of time, you're looking for issues, the software can help you get there faster.
[00:04:27] Tom Moore: It also helps our new technicians, uh, for with training, they actually get to see what a seasoned tech would look at on our faults.
[00:04:34] Uh, so they're not just starting from scratch either. They probably wouldn't have never been able to diagnose this problem without all the help that.
[00:04:42] James Dice: Totally. And just to set the context for the rest of this discussion, I'd love to just sort of rattle off a couple questions rapid fire round for you before we get into the details here.
[00:04:51] Who's the software vendor that you guys are using today?
[00:04:54] Tom Moore: We use Clockworks through our Schneider partner, the Base Point Group.
[00:04:57] James Dice: Cool. And how many buildings is, uh, the [00:05:00] software installed in?
[00:05:01] Tom Moore: Uh, 47 currently, uh, we've had up to 54. I think at one time I think about 10 buildings. We decided we weren't seeing the benefits, so, uh, we reduced and then added a few.
[00:05:09] But 47 is what we're currently staying at.
[00:05:13] James Dice: And what's the total square footage?
[00:05:14] Tom Moore: 6 million. 880,000.
[00:05:16] James Dice: And when did the project start?
[00:05:18] Tom Moore: 2014.
[00:05:20] James Dice: What sort of results, outcomes have you guys seen that you're measuring, uh, over that time?
[00:05:26] Tom Moore: You know, we use tasks to show what we've looked at and what we've closed out, and we've co closed out over 2100 tasks in that, which is a considerable amount stuff.
[00:05:36] Um, we've saved over two and a half million dollars proven dollars, not avoidable cost proven savings through our energy bill. So that's, that's how we're ging our success.
[00:05:45] James Dice: Awesome. And. Before we bring, we have a few more friends here before we bring them on, can you talk about the deployment and sort of integrating the software into the operations?
[00:05:57] Tom Moore: Sure. Um, we started out, [00:06:00] as a lot of people do, we thought we could self-manage, you know, nobody's better than us. And, uh, And doing maintenance stuff. So we wanted to bring everything in house. We were gonna have it on-prem. We were gonna make our own faults, we were gonna make our own graphics, uh, we were gonna do all this stuff Since we were a partner with, with Microsoft, we went with an icons platform, uh, which is a.
[00:06:20] Does exactly what it's supposed to do. Uh, but it just didn't fit us. After that first year, we were spending way too much time building our own graphics, doing all that stuff that we realized why not have this team of people from all around the world developing the program for us. So we went out for an rfp and that's how we got hooked up with Clockworks.
[00:06:40] Uh, once they got on board, that's when things really, really started to ramp up in my opinion. As far as seeing savings and different things like that, we decided to do a pilot. 10 buildings, a mixture, not necessarily who we're gonna save the most money on, but we wanted classrooms. Uh, we wanted inner energy buildings, so like research labs, some [00:07:00] of the athletic facilities, uh, amounts of equipment, uh, high and low.
[00:07:04] We wanted to try all those so we can, you know, base what we would move forward with if this was successful. Uh, so it was very successful. So we went with a round two. I believe we did 23 more buildings in round two. Uh, we did a lot better selection then. Uh, it wasn't so much we're trying to discover. We already figured that out during that first pilot.
[00:07:23] Um, so I think the first pilot, they onboarded us in about three months. The second one, I think took a little bit longer, more like eight months to get the second one onboarded, which is understandable. There's much more, um, Work to do there. Um, I will say in their defense, I was telling him to slow down.
[00:07:40] How am I gonna do all these buildings checked out and everything else? So what I was saying, you guys gotta slow down. You gotta slow down. Which, um, I'll never say again, but it was amazing how quickly they onboarded it, where we just spent a year doing one building. You know, they brought on 43 buildings in less than 11 months.
[00:07:56] But once we had all that, that going, we decided to form this, our [00:08:00] group A, we got about 3,500 faults we could be acting on. So, We got plenty of things to do every day.
[00:08:06] James Dice: Yeah, I love that story because it shows the journey you went on one software provider, it didn't quite work for us. Thought we could do a lot more in-house than we, than we actually could.
[00:08:16] So we pivoted, went out for rfp, did another pilot, and then rolled out in a large way and then built the team, developed the processes. Um, so we're gonna focus on those two things. Last things. We're not gonna go into why you selected a certain software. Today we're gonna talk about the team and the processes, and the idea here is to dive into those two things because it really, I think that's where we're at sort of as an industry is that I think a lot of people have validated that this tool is needed.
[00:08:45] Especially when you have more buildings than your operations folks can get a grasp on, right? You have a lot of deferred maintenance, you have stuff breaking all the time, you have a lot of hot and cold calls. People have realized that f d D is an important tool, but I don't think a [00:09:00] lot of people have figured out how to integrate it into their team and, and, and make it work on a day-to-day basis.
[00:09:06] So now let's bring in Brad and Katie. They've been ghosting in the background here, and then they're gonna bring him onto the front stage. So Brad, let's start with you. Can you, uh, do a little introduction to yourself and talk about what your role is on the team?
[00:09:20] Brad Dameron: Yeah. I'm Brad Damron. Been at the university now for almost four years, and I was kind of brought in to.
[00:09:28] I think try to take the FTD to the next level and really branch out. You know, initially when they got the software, you know, it's, you get a lot of the low-hanging fruit. Oh. You get these big projects and big savings and those are pretty easy to pick and choose from. And you know, it's gets people excited.
[00:09:46] But then after you've had it for a while, okay, the savings kind of goes down and down if you're doing your job. So, okay, now what do we do with it? Well, we need to refocus and, okay, how do we use this as a maintenance [00:10:00] software and how do we be more proactive rather than just, okay, it's finding these things.
[00:10:06] Okay, what are we gonna find before it becomes a big problem? That's kind of the more of the push, and that's where. More of my role, I guess, is, you know, trying to be that more proactive person. We're looking for these things that we can catch before they become a big problem, and then actually getting it out to the field, getting it out to as many people as possible so we can get as much done using the software as we can and just trying to be more efficient.
[00:10:33] James Dice: Cool. And we're gonna come back to a lot of those process oriented things that you're sort of delegating tasks out and that kind of thing. Katie, can you jump in and introduce yourself, uh, and talk about your, your role on the team?
[00:10:46] Katie Rossmann: I'm Katie Rossman. I, uh, was on the team with Tom that helped to, um, implement the F D V program at the University of Iowa.
[00:10:55] I sort of had a dual hat of energy engineer when I first started the program, [00:11:00] and then I moved into more of a. Leadership role as the, uh, manager of building analytics and commissioning, but I still really wore that energy hat as part of a member of the, the ARG group. I have now since transitioned from my position at the University of Iowa and I work actually on the Clockworks Analytics side.
[00:11:18] I've been there for about two years. I am, uh, the director of the Technical Operations Center, uh, which I lead up the team of service engineers that help clients like the University of Iowa with. Process improvement, uh, helping them use the tool, find value out of the tool. So I basically would do the same thing that I did at the University of Iowa, but for a broader audience at Clockworks.
[00:11:41] James Dice: Yeah, so you can weigh in on how you guys did it at Iowa when you were there. You can also weigh in on best practices that you've seen since you've left, uh, in terms of people integrating the technology into operations. Absolutely. Can you guys, starting with Scott, talk about the other people on the team and what their, sort of, what their other roles are.
[00:11:59] All [00:12:00] of these people aren't here, so we won't drag their name through the mud at all, but, uh, talk about what they're doing on the team.
[00:12:07] Tom Moore: So Scott Soner is our controls technician, controls lead as part of our group here. He's really involved with the programming side of stuff. He'll definitely go out in the field and, and help with that stuff, but with this platform you do find a lot of programming changes that you need to have.
[00:12:21] So he's, he's responsible for either making himself or getting it to the other people. On the controls group that we have here at Iowa, we're very. Very lucky at Iowa to have a controls group, as I think it's up to eight people now, uh, that Jude does think nothing but programming and, and and BS work.
[00:12:37] James Dice: Awesome. And, and who else would you guys consider to be on the, the core team?
[00:12:42] Tom Moore: An IT professional for sure. Ours have to be guy named Sarm, but, uh, without the IT professional, I don't think we, we would be where we're, where we're at for sure.
[00:12:51] James Dice: Totally. And, and do you, can you just talk about a little bit in more detail of what, what his role is on the team?
[00:12:59] Tom Moore: Yeah, so [00:13:00] during our RFP he was very integral. Um, he was telling us what, what was real, what wasn't, what these vendors were telling us. He was telling us how who we could integrate and who we couldn't integrate with. Uh, it wasn't us making a decision and going to it and telling him to make it work. It, uh, he was really, really important, uh, to make sure as part of the selection committee, um, On what we were gonna choose.
[00:13:22] So then once that happens, he runs all the background stuff, make sure the connections are there, the firewalls up, and doing all that good stuff. He also, he tells us when we need to change our, I mean, literally some of our, our programming stuff, he's, he's helped out with. So, but definitely in the beginning, that role gets really diminished after you get rolling.
[00:13:42] But in the beginning, you have to have it, or, or you're just, you're gonna be wasting a bunch of time. Because you're gonna pick something, you're gonna take it back to your IT professional and they're gonna say, we can't make that work. So now we gotta go to number two. Had we had him on the first, uh, pilot, more involved, I think we would've probably made some different [00:14:00] decisions, uh, which, so that we definitely made in the second pilot.
[00:14:04] James Dice: Got it. Okay. All right. Who else on the team?
[00:14:10] Tom Moore: I would say all of our, all of our frontline techs and our managers, were really trying to integrate them much more than we had in the past. So I would say that they're, they're definitely part of our team.
[00:14:19] James Dice: Got it. So it's not just this, this external team that's sort of throwing stuff at the frontline technicians.
[00:14:26] It's Right. These people are part of the team and we're sort of trying to integrate it into their, their daily workflow. Yeah. That's awesome. Yeah. So. I understand with this team, when you guys were building it, Katie, there was something that you were arguing maybe with Tom about that
[00:14:43] Katie Rossmann: friendly banter.
[00:14:43] James Dice: In retrospect.
[00:14:44] Katie Rossmann: Friendly banter.
[00:14:45] Tom Moore: Friendly banter. There you go. There was no arguing.
[00:14:48] James Dice: In retrospect, it looks like you're on, you're on Tom's side now. Can you talk about, uh, that sort of friendly banter argument?
[00:14:56] Katie Rossmann: Yes. So to be clear, Tom and I are very much peers as [00:15:00] we were sort of given our. Our charge to go figure out what this F d, D thing is.
[00:15:05] And we had talked to some other folks who had been using the tool. It had been sort of sold to us as an energy tool. And so, you know, my thinking was instantly like, this is an energy management functionality. This is something that energy managers take. We look for problems and we communicate it like in a more classic.
[00:15:25] Energy conservation measure, energy project, spreadsheet, you know what I mean? And track it outside of, of your maintenance organization. And Tom kept pushing me like, no, Katie, this needs to be something that maintenance does. Maintenance needs to have a really integral role in this tool. And, um, and I, I, it was very much a difficult mindset for me to grasp that.
[00:15:47] Um, it can't be the more. Kind of rigid, uh, project implementation that needed to be part of our day-to-day lives and how we do maintenance. And so, um, I will never live it down, but Tom was a hundred percent [00:16:00] right and I was wrong. That I really believe that was integral to our success is the, the integration to our c m s, the, um, the use of work orders to push action instead of relying on some external tool that are, um, are.
[00:16:16] Our maintenance people don't speak tasks. They speak work orders. And so the more it looks like their day-to-day hot and cold call, the better it is, right? So if we can make that push of that F D D resolution look like a work order, then it's much easier for the organization to adopt it. And also they get.
[00:16:36] Much better adoption when it's someone like Brad who's sending the work order out, who can go and get his hands dirty and fix the problem. And you know, if they need help, he can go help them. Whereas if it had been me sitting at my desk looking at energy numbers in a spreadsheet, I don't think there would've been that same buy-in.
[00:16:53] So I think that was really important that we had well respected, um, really good technicians that [00:17:00] were already fixing broken stuff anyway, just come and fix it in a different way.
[00:17:06] James Dice: I love this insight because you know, in a lot of organizations, an energy engineer could be an external consultant. It could be someone in a different department, it could be someone on the portfolio level that's kind of outside of the, the group.
[00:17:18] They're not boots on the ground, they're not there every day fixing stuff, right? So the fact that you guys decided, well, Tom overruled you there and decided didn't.
[00:17:27] Katie Rossmann: No, no, no. It very bad. No other. It was
[00:17:30] Tom Moore: very fun. Finally, her truth,
[00:17:40] the cmms. This is, we treat these like any other work order. They do not get special treatment when it goes out to the frontline. And I should have said that earlier. So that also helps with the implementation too, because we have what our customer timeframe expect expectations of when tickets are gonna be finished.
[00:17:55] Uh, so we are able to use that metric to see how successful we were being with these [00:18:00] frontline folks.
[00:18:01] James Dice: Totally.
[00:18:02] Katie Rossmann: I do think this actually really speaks to the same decision we came to with our, what platform we used was what our organization was good at. I've seen this energy management run F D D programs work well at other organizations, but with the resources we had at Iowa, the funding sources we had at Iowa.
[00:18:22] The levers we had to pull to execute work. If it wasn't gonna work, if it was coming through as an energy project, just based on history at the university and, and the resources that we had at the time, it was going to be a much more successful program if it was run through our maintenance organization and we had such good buy-in from leadership with Tom that like, you know, that helped a lot too, right?
[00:18:43] That, that we were both at the table together as peers kind of coming up with what this program looked like. I think that was also really helpful in, in our success. And we do obviously like still like each other, so it must have worked.
[00:18:56] James Dice: Yeah.
[00:18:58] Tom Moore: School.[00:19:00]
[00:19:04] James Dice: So before we move on to the actual process, um, Which is one of the things I'm most excited about here to talk about the big ass flow chart. Um, Tom, I wanna see if you have any advice for people that are trying to select who should I make this analytics super user on my team? Should it be the top technicians?
[00:19:22] I think a lot of people say, no, I want my top technicians out there still doing what they were doing before. They're the most productive people. I think they say. Maybe I'll. You know, pluck this newcomer and, and have them be the person. Why, why did you guys select the top technicians?
[00:19:39] Tom Moore: Because the, they're still doing work, right?
[00:19:41] I mean, this is not like we, you know, drug the work system down in the shop once they left because they were still doing stuff in that shop. Uh, but it may not not be all day. Right. And, Really as good stewards for the university, we need to put the best people in every best situation that fits that situation the best.
[00:19:59] [00:20:00] We're distributed. We're not a central, uh, maintenance group. We have five shops on campus. Um, it's great to have these, this group just be that single point of truth, right? Like, if I have a problem, I'm gonna call them, this is what I'm looking for, this, you know, they're watching my back with this program because they might be able to get something fixed beforehand.
[00:20:20] Getting projects done that never would've got done before, right? Because without we have the, the data and the proof to say, Hey, this is, you know, we need to do this. We we're, we could be saving, you know, $25,000 a year just by, you know, getting this air handler outta here. Uh, selfishly I knew I needed some people that were well respected on campus, you know, known to be teachers with others, and known to get the job done, helped out
[00:20:41] Katie Rossmann: and, and they, they were doing F D D.
[00:20:44] On their own anyway, right? So they were already manually looking at the b a s in the morning to try to find problems. So it's just replacing the tool was something that's easier for them.
[00:20:54] James Dice: Absolutely. All right, let's talk about the big ass flow chart. I, I first saw this, uh, last [00:21:00] fall when I was with you, you all in Boston, uh, which was super fun.
[00:21:04] I was very impressed by the detail in which you're laying out this like process flow. Um, Brad, do you wanna take us through, describe what this is? We'll, we'll put a link to it in the show notes. We'll, we'll share it like this actual flow chart with everyone that's listening to this. You can find it on our website.
[00:21:22] Um, but Brad, can you talk us through it?
[00:21:25] Brad Dameron: Yeah, yeah. This is actually, uh, One of the first things I helped with when I started here is we said, you know, we really need a flow chart so we can explain well, both to ourselves and everyone else, what does it look like when a fault comes in? What are our duties?
[00:21:42] And yeah, the number one thing is, uh, you know, is it a true analytic? You know, people think, well, yeah, it just spit it out to us and we just automatically put out a work order or something. First is evaluate, is this. Is what this is telling me true? [00:22:00] Is it a sensor error? Is it a, you know, is it a mechanical thing or does this not make sense at all?
[00:22:06] I mean, you know, not every fault is a real issue. And so gathering all that information with the software, we get all the trends and we can see all the sensors that are involved, how they decided that this was an issue. And oh, you still gotta put a human brain to it at some point and say, okay, does this make sense?
[00:22:28] If it doesn't make sense to us, we have regular meetings with the software provider that we can take issues to. It's like, you know what? This doesn't make sense to us. We don't think this is a true fall, or, oh, can we adjust this fall? You know, this is too tight a tolerance. We've had to do that many times.
[00:22:47] You know, Brian and I are the first line of defense, so we're looking at these faults day in and day out. We both have over 25 years experience in HVAC and controls. So between the two of us 50 years experience, [00:23:00] we can kind of tell, okay, you know, I got a pretty good idea what this is. Then I can say, I can either send it to the group area maintenance guys and say, well, I want you to look at this.
[00:23:11] I'm pretty sure this is the issue, and if it's not that, then go ahead and get back to me. That's the ideal situation. So you know what? This is kind of a bigger scale thing. Then we'll go out ourselves and put our eyes on it, you know, put meters to it and verify, okay, this is a issue. Okay, we know exactly now what trade we need to get in there.
[00:23:36] Okay, we need electrician, or we need a pipe pitter to change out a valve. This valve is failed. Um, or is it an electrical issue or. You know what? This is even bigger scale. We need to create a project cuz we have around 3,500 faults per day that we're trying to prioritize. And the software does try and bring up the top scoring faults.
[00:23:59] [00:24:00] So this is where we show the most money it's costing you. Or we can sort by comfort issues. This is what's causing the biggest comfort issues that you might wanna address. Or we can sort by maintenance issues. Okay, this is a mechanical failure. The top mechanical failures that we've, you know, come across and we kind of have different focuses on different days or even maybe even weeks or months.
[00:24:25] It's, that's where I think it takes somebody that has that experience and can decipher what direction you're going with that. Also, we figured out that the software actually provides a link. To all the trends and all the data that it used to find that fault. We attach that right to the work order so the tech out in the field can just click on it now and go right to the fault.
[00:24:50] And they've really been loving that too. And you get a lot more buy in that way. It's something we've learned that that that goes a long way.
[00:24:58] James Dice: Yeah, sure. I'm [00:25:00] sure. Thanks for taking us through that, Katie. I'm wondering, so one of the things I think is interesting here is we have the integration of two systems, right?
[00:25:07] We have F D, D, and we have a work order system or a cmms. Those two pieces of software are integrated with each other, but it doesn't seem like that integration is automatic, really. It's not like every fault is coming in and creating a work order. So, Katie or Brad, however you guys want to take this, but can you talk about, um, why.
[00:25:29] It's only some of them, and maybe it's obvious, but I think it's not obvious for the the tech folks that are just like integrating everything together. Right. Why is that a manual decision of what gets brought in from the F D D to the work order system?
[00:25:44] Katie Rossmann: I think the main reason that it is a manual process.
[00:25:47] Is, um, because of what Brad was speaking about, about that kind of pre-vetting of the diagnostic results, your output is only gonna be as good as the data it's consuming. So sometimes you'll have issues with sensors that are causing [00:26:00] problems, you'll have issues with. The way that diagnostic might be configured is, is based upon a sequence of operations that no longer is used anymore, or it's based upon assumptions that Iowa no longer.
[00:26:13] It makes anymore. Right? So having the human input of generating that work order gives it just kind of that first bet before you send it out to the field to go look at it. You're doing that, that kind of initial triage to say, um, okay, here's where the issue is. The other reason that it's nice is, is because a lot of times what you're looking at potentially are.
[00:26:35] A list of symptoms and then a problem, right? And being able to see all of those symptoms in tandem with the problem allows you to kind of say, okay, the root cause of this issue is this one valve. So it also allows you to kind of send that work order out and say, pay attention to this valve. There's all of these other symptoms that are happening, but the thing that you need to fix is the valve.
[00:26:55] So it does kind of allow you to, to like when you're actually taking action, give [00:27:00] directed information to the field. Right. And, and when you're getting that diagnostic result, so kind of to Brad's point, you're seeing all of those symptoms and the problem identified for you, right? And you're seeing like a list of recommended corrected actions.
[00:27:14] When you create that, that work order, um, it's gonna show all of those things together, right? Because they're kind of, they're all interrelated. And so if that were to automatically send out. It might give, you know, confusing instructions to the technician too. So Brad's able to say, okay, I see all of this information at once.
[00:27:34] This is the problem. And kind of narrow down on that.
[00:27:39] James Dice: Amazing. So I, I want to kind of repeat sort of the, the big S flow chart, sort of back to you guys. There's one loop of, uh, an ongoing meeting and tasks around just making sure the software is doing what it's supposed to be due is, is keeping updated, is um, Sort of tailored to how you guys wanna see it.
[00:27:59] And then there's another [00:28:00] loop around tasks and validating tasks, tracking tasks, getting them implemented. So that's an ongoing meeting. Repetitive meeting as well. And then there's this triage piece that Brad and Brian are two sort of super users are saying. I'm gonna assign this to the right trade. I'm gonna track this, I'm gonna support them in the implementation, and then I'm gonna see if it's resolved after the fact.
[00:28:24] And so it's like kind of like three different loops going on. That's really cool. That's really awesome. So let's do a little storytelling. Is there one project that comes to mind, Tom, that you would tell to another university at a conference saying, lemme tell you this cool story about what we did in our F D D program?
[00:28:45] Tom Moore: So this is one when we, with the original software and when we first started doing this, right? So, uh, this one was kind of my aha moment. It does work. Uh uh, so we just built a new huge wet lab building, a biomedical research building, a [00:29:00] six stories of wet labs, and then another 40. Feet or poor stories in the ground with supporting equipment and oar space and different things like that.
[00:29:07] So, uh, this was the building we picked to do first had to pick the most complicated building we had, newest building we had on campus, which I think is great cuz we learned a lot by doing that as opposed to if we just had a couple quick wins we would've never made in the decisions we made. So, um, the guys found out that they were not getting the discharge air temperature that they thought they should out of a va out of a bunch of VAVs in the scene.
[00:29:31] Same room, right? So they go out there, they start setting up their ladders, and the department head comes home and goes, what are you guys doing in here? And they're like, well, we've, we've run the software over here, over our building automation system that's telling us that you're not getting the heat that you need to get out of these coils.
[00:29:49] And they're like, well, it's fine to us, but if you wanna go ahead and check it out. So Jeff and Bob get up there and we had to have the pipes reins insulated as part of one of our. Punch alerts, checks for this [00:30:00] building. Insulator came through, insulated and shut all the hand supply and, and returned hand battles off to all the VAVs.
[00:30:06] So we had no hot water going to those VAs. So Jeff and Bob went up there, opened the ball up, and the, you should, it was like, They almost applauded 'em as they left. They're like, this is the best it's felt since we've been here. And they're like, well, why didn't you call us? And they're, they said, well, it's a new building.
[00:30:21] We just assumed this is what we were gonna get. I just thought it was supposed to be like this. Yeah. So win different levels. We had win with the customer, win with Software Works. We're. We really got into this hoping we could do predictive maintenance. Right. Um, you know, with some of the AI stuff that's coming out and different things.
[00:30:39] So that to me was about as predictive as you can get. Right. We, we, we solved the problem before it became a problem and it was a problem, but, uh, the customer didn't know they had a problem.
[00:30:49] James Dice: Yeah. So the, the output on the valve was, I need heat. Right. But then you had a manual valve those closed down not letting it get any water.
[00:30:56] Correct. And, and, I guess, how long would it take to [00:31:00] find something like that? You wouldn't find it until it's the coldest day of the year or something. And yeah,
[00:31:04] Tom Moore: till, till they complained, to be honest. Yeah.
[00:31:07] James Dice: Yes. So the last 10 minutes we have here, I, I would love to talk about some lessons learned here and we've kind of gone through these together before we, we hit record here.
[00:31:17] So I'm gonna sort of feed them to you guys and then I want you guys to sort of talk about those. So the first one, and I think this is my near and dear up to my heart, because it sounds like there was some pushback from technicians that were saying like, You know, this, all this analysis that this software is doing, that's, that's my stuff.
[00:31:36] That's my magic. That's where, that's my career that you're sort of automating away. Um, how have you guys sort of managed that, that piece of this, because obviously on one hand we're using technology to. Get more out of less people. But on the other hand, if someone really likes trying to go find problems and finding the needle in the haystack manually, [00:32:00] you might upset them.
[00:32:02] Brad Dameron: It is still an issue for some people and it's, it's showing them that, you know, most of the things that these, that the software finds. Is not things that you're gonna find just stumbling across it. You know, if you're sitting there looking at your b a s all day, every day, yeah, you're gonna catch it, but you have work to do and it's convincing then that we're not there looking over your shoulder.
[00:32:29] We're not trying to make you look bad, we're trying to, we're there to help. You know, this software is helping you do your job better and it's. Finding the needle in the haystack. It's not something you're probably going to find. You know, those things are reactive. You know, we're not looking for the reactive stuff.
[00:32:47] We're trying to find it before it becomes a, a big deal. And it's just, it's, it's educational. It's just getting out there, talking to the people, showing them what it's all about, and showing [00:33:00] them that we're not here to make you look bad. It's not going to make you look bad. It's, you know, it's just another tool.
[00:33:06] In the toolbox and that's what we, we really try to emphasize. This is a tool that we're using just like all your other tools.
[00:33:15] Tom Moore: They take pride in when we have a $25,000 energy save. They're involved. They're helping with that fix. Having those kind of winning situations really helps. It also helps we, we spur projects that improve their space.
[00:33:28] Right that we weren't getting money for before. So I think through several projects that we had done through our Im u Blitz and, and different things, and we made the building that they take care of so much better, they see the benefit of this. Right? So it's kinda
[00:33:41] going,
[00:33:42] Brad Dameron: we actually, yeah, we talk about, you know, peeling the onion.
[00:33:46] This fall may start pretty small and the energy savings on this fault may only be a few dollars. By the time you unpack that and you keep peeling the onion back and peeling it back and peeling it back, this thing just gets grows and grows and grows and it's like, you [00:34:00] know what? This is actually a big deal.
[00:34:02] We can submit this as an energy project. And I mean, we've had some big success stories.
[00:34:08] James Dice: Totally. Okay. The next one we had was evaluating where your strengths are. It sounds like you guys talked about this a little earlier. There was a little bit of like biting off more than you could chew at the beginning.
[00:34:20] So how have you figured out as an organization there's a lot to do here? IT software, programming database. Um, Obviously all of the implementation we've been talking about, there's a ton to do in this process. How have you decided what to take on, what to outsource, et cetera?
[00:34:40] Katie Rossmann: So when we initially did our pilot and we were looking to self perform everything, I think like one of the biggest data points that proves that there's a.
[00:34:51] Something to be said for letting someone else do something that's better at it. And that's the onboarding time. So when we onboarded that one building and our [00:35:00] pilot and we did all of the self-performing, it came down to, I think it took us six months. To just get points communicating felt like just the learning curve of figuring out the integration and how to point map everything in, and then writing faults and the management of those faults, right?
[00:35:17] The change management of, oh this, this air handler operates this way, this one operates slightly different. And like trying to track all of those changes. We just didn't have the tools, the resources, the people to manage all of that. It was basically just going through me to make any adjustments to the analytic results.
[00:35:36] And, and so I think that alone was sort of like, we probably shouldn't do this in a vacuum. Right? There's a, there's a beauty to being able to crowdsource some of this stuff that people have already. The case I really made, and I was like, I think we need to pivot here, was. There are people all over the United States writing the same economizer fault 10 different ways.
[00:35:55] Right. You know, it's like, why am I the 11th? You know, so I, it just, it feels like [00:36:00] there was some, some like scalability that could happen through kind of a crowdsource model. So that's one of the main things right away that we were like, this is not something that we can take on as an organization. That's not our strength.
[00:36:11] We have always been very particular that the troubleshooting and determination that something is. Is actionable. We have owned and that's remained, that's been the, like our bread and butter. And that was really from the very beginning was we wanna own deciding what we do in our organization as far as what tasks and work orders we say are actionable, right?
[00:36:33] Because we understand our business model, we understand the, our priorities and what's important to us. So that was something we always really wanted to own.
[00:36:42] James Dice: And this is a thing that, you know, you guys have seen a couple different f d D vendors. I've seen like all of them. And, um, it's important for people that are listening to this, that are just starting down this journey.
[00:36:53] Not all f d D products can do what Katie just said in terms of crowdsourcing and sharing these [00:37:00] concepts across customers, across buildings, across geographies, across. Units like in, in Europe or Asia or whatever. And so one of the things we're trying to do with our partner program is really set standards for, if you're selecting F D D, it needs to be able to do this.
[00:37:16] And I think that's one of the things that's really important, is being able to use what other people have already written. The other 10 people that are writing economizer rules, the the product should be able to make it so that we're not recreating the wheel. Every time. The third lesson learned you guys gave was having leadership buy-in from the beginning.
[00:37:36] Could you guys just tell that story of how this kind of started with Don and his sort of vision that sort of helped you guys get this off the ground? I.
[00:37:45] Katie Rossmann: Don gk, who was the AVP at the time at Iowa, came to Tom and I and said, you know, I've read this article, uh, this Doug Tweer also was, was pretty instrumental in this.
[00:37:56] And there was an article that had been written about Microsoft's [00:38:00] implementation of F D D. It probably was from like 2008 because this, that's when this journey really started. So I think even pre, pre, Tom and I, you know, Iowa had made a trip out to Microsoft, had had visited their campus, had seen their F D D program in.
[00:38:14] In life and then came back and kind of told Tom and I to, to make it work, right. So then we, we also took a trip out there and we, we talked to the people that were making their F d D program work, so we kind of asked some questions about it as we were implementing our pilot. But from the very beginning, Don was a, a very good champion for our program and one of the biggest lessons that he taught, To like very nervous people about something going wrong is to not be afraid of failure.
[00:38:41] Right? So, so keep going, right? And take some of those risks. And if it fails, we can always change course. And that was really important guidance for us as we were looking for more like, why are we doing this? Are we wasting time? And he just kept pushing us to just, just test the limits and the boundaries, see what could work.[00:39:00]
[00:39:00] And when we made this decision, we went out for RFP and the decision was sort of like, This vendor we're picking is not the one that we've spent all this time and resources on. Is that a negative here? And it was just sort of like, that was a a year of learning and we need to pivot if it's the better option for us going forward.
[00:39:18] And um, it made that choice a lot easier for us to, to make that switch because so much time had been invested in that initial pilot.
[00:39:27] Tom Moore: And that went all the way up through the president's office. He did a great job. He sold it to them too. But I ran into him in the hallway about six months after he started, and he's asking me how it's going, and I was listing off stuff that wasn't working and he goes, I want you to stop right now.
[00:39:41] From now on. I only want to hear what's working. I don't want to hear what's not working. It's your job to figure out why it isn't working, not mine. So I only want to hear the good things, you know? So that was one thing that was like, he was basically saying to me, I don't care if you screw up Tom, I'm never gonna know about it.
[00:39:55] Even if I do, I know it's part of the process. You know, 10,000 tries to get a light bulb. [00:40:00] Uh, so I, that helped me out. Tremendously.
[00:40:02] James Dice: Yeah. So somebody that understands that this is a, a process that we're learning here. We're adopting something new, there's a lot of change management involved and and can kind of roll with the punches a little bit.
[00:40:13] That's awesome. So I wanna thank you guys so much. This has been super in insightful. I think a lot of people will learn a lot, I think. That original Microsoft f d d article was one of the reasons that I kind of went down the path that I went on. It's a, it's an inspiration still because think about all the people that have gone down the path since they read that.
[00:40:32] I'm hoping that when people listen to this, they can kind of have a, a similar light bulb. Come on. So before we close this out, I want ask each of you anything that we've missed that you wanna quickly say before we close off.
[00:40:47] Tom Moore: Just having the right team is a big deal. You gotta have the right players.
[00:40:50] We're successful because we picked, like, got lucky and picked the right players and you know, we're okay with failure. You're gonna fail cause you can't, you [00:41:00] know, all those lessons were learning lessons for us. Right. We wouldn't be where we're at without that first program. We knew what we wanted after that.
[00:41:05] We knew what we needed.
[00:41:08] James Dice: Yeah, totally. Katie, Brad, any any closing insights?
[00:41:11] Katie Rossmann: I will actually echo this. This team team strength I think was also really important to our success. I loved this program. I could talk about it all day long until I'm blue in the face. It's not just, we're not just, I. Advertising for the University of Iowa truly was a real joy to work with this team, and I think the thing that I liked the most about it was that it was truly results driven, right?
[00:41:34] You can't hide behind fake numbers because people will, Notice when your bills don't go down, or when work orders don't get closed, or when your numbers never move, right? There are results that you can tie to your success. And so it was a really, a really meaningful part of my career as being able to work on a team to, to implement a program that has lasted so long, um, at a big institution.
[00:41:58] James Dice: Awesome. How about you, Brad? [00:42:00]
[00:42:00] Brad Dameron: Yeah, I mean, I would echo, you know, having that team of people that are results driven. I think cuz that's, it's very easy to see your results here and that's something that I'm driven by. You know, I wanna see results from my work and you get instant feedback. Now the only other thing I would add is, You know, the educational as aspect, oh, from the top to the bottom.
[00:42:23] That's one of the hurdles. I mean, it's just educating people from the top to the bottom. This is a tool and this is how it gets used, and these are the benefits and it's, it's constant, you know, we're how many years in and we're still, you know, educating people and it's, it's just going to take time and, and education and that was the only other thing I wanted to add.
[00:42:45] James Dice: All right. Thanks so much for, for coming to, to, to share your story here. This is a great story and I think all people are gonna get a lot out of it. So thank you so much.
[00:42:56] Rosy Khalife: Okay, friends, as we're trying these new formats, please [00:43:00] let us know what you think in your podcast player right now, or on the episode page on our website. There's a link to a survey for this specific episode. We'd love to hear from you and we wanna hear your feedback. Also, don't forget to sign up for the Nexus newsletter. Or invite your coworkers and friends with a link below.
[00:43:17] Catch you next time.
Head over to Nexus Connect and see what’s new in the community. Don’t forget to check out the latest member-only events.
Go to Nexus ConnectJoin Nexus Pro and get full access including invite-only member gatherings, access to the community chatroom Nexus Connect, networking opportunities, and deep dive essays.
Sign Up
Nexus Labs exists to move the smart buildings industry forward, without the fluff.
On Wednesday, we send out the renowned (and free) Nexus Newsletter.