Scott Davies on How PTC Is Shaping the Future of Automotive Innovation
In this episode, we speak with Scott Davies, former McLaren powertrain leader and, at the time of this conversation, Principal Business Development Manager at PTC.
This article was first published on
the-next-byte-wevolver.simplecast.comIn this episode, we speak with Scott Davies, former McLaren powertrain leader and, at the time of this conversation, Principal Business Development Manager at PTC. Scott traces his career from working with 28,000-horsepower ship engines and historic Formula One cars to developing powertrains at Jaguar Land Rover and McLaren.
Scott explains how connected data, effective product lifecycle management, and a strong digital thread can help engineering organizations manage complexity and develop products faster. Drawing on the accelerated development of the McLaren Senna, he shows how his team combined trustworthy data, reusable validated components, close supplier relationships, and carefully targeted testing to move from a clean sheet to a finished vehicle in just months.
The conversation also explores how companies can connect globally distributed engineering teams, remove processes that consume time without adding value, incorporate feedback from experienced technicians, and give engineers more capacity to create. Scott closes with his perspective on the future of mobility and why the next era of automotive development may be eclectic rather than simply electric.
Daniel
Alright folks, as you heard, we've got Scott on the podcast today. Scott Davies, before we jump into any further detail, could you give us a quick intro of who you are and what you do?
Scott Davies
Yeah, so Scott Davies. My title at PTC is Principal Business Development Manager. And part of my role here at PTC is to help our customers along this journey of getting themselves into the 21st century, really being able to accelerate engineering, get that right first-time mindset in place and build a really strong infrastructure that can be scalable for the future and to be able to be prepared for whatever the future might bring them. So with my experience and background, I'm able to help speak the language because I've lived a life and to be able to help encourage them along the way that it can be done, and to be able to help piece together what that roadmap would look like. So I've been at PTC eighteen months, looking at the calendar here, and before that I've got nearly twenty years of experience in the automotive industry, working on some pretty cool projects. And then even before that I did a brief stint in the military as well. So being able to apply my systems engineering experience, my development and design and project management and leadership experience, there's a means where I can show up qualified to be able to sit down and talk to these customers and help them piece together what that future would look like for them and hold their hand along the way. So that's my opener.
Daniel
Well, so before we jump into experience, which is something that Fribo and I are both excited to talk about, I think you brushed on it, but it would be helpful to do the thirty second explainer for someone who's not an engineer using product lifecycle management software to understand exactly how PTC is helping move the needle and what that means in laypersons' terms, if I was not an engineer using it. What does that mean to me, what you're working on on a day to day basis?
Scott Davies
Sure, okay. So the 32nd. Your company makes something. You make something today. You're making it, but in volume, you've got some complexity. You've got all these people involved on having this thing come to life. How do you manage the interactions? How do you manage who's building what? Where does it come from? How much does it cost? And who's the guy that designed it? And why are we building it the first place? Being able to put that together is that means of being able to have this digital connectivity now. And we would call it the digital thread. Others have called it a digital twin. But there's a means of being able to have it within a few mouse clicks to be able to say, I know where it's going to be built. I know who's building it. I know how much it weighs, because my logistics guy needs to be able to put it the truck. But then to be able to see this through its life cycle. That's why we call it the lifecycle management, from that napkin creation, sitting at the bar, hey, I want to design this, all the way through to I've made 110 billion of these. And what do we do for its end of life even as well? Some countries actually dictate end of life. So being able to connect all that together, that's just one aspect of what PTC does. Through the product lifecycle management piece of it, there's a ton of other little pieces that we connect together to truly support all of these customers that are either doing discrete engineering or even process engineering. Think Coca-Cola making the syrup for their drinks.
That sort of process, I make yogurt, I make syrup, those sorts of things. PTC's expertise is being able to support multiple industries, automotive, med tech, electronics and high tech, aerospace and defense. Each of these, we've got a number of big names and labels and companies that we've supported for years. It's a 40-year-old company now. So we've seen a thing or two. And so being able to support that, that's who our footprint is. And we're always excited to talk to new customers. But we'd be interested even to have our current customers go talk to these new customers as well. It's our thing. So
Daniel
And so when we're talking about in the context of a lot of these industries that you mentioned, you've lived in, you've touched, you've had the experience of being an engineer, sitting in that seat, needing someone to help keep you coordinated with the rest of the parts of the system. Scott, I'd love to jump way back to the beginning of your professional story, so to speak. Understand how you got into the field you got into and your progression from where you started to where you are today and any important tidbits along the way. It's important for us to understand the story behind what you're working on today and why your experience is relevant to what we want to talk about later in the episode.
Scott Davies
Sure. Yeah, no, I'd love to talk about that. So I should just start from the beginning.
Daniel
Yeah, hit us.
Scott Davies
Well, so I was born in an early age. I'm teasing.
Daniel
Ha ha ha. Relatable.
Scott Davies
No, totally, right? Okay, so growing up, my dad was always our big inspiration for how to fix things. We never had the serviceman come to our house. So I grew up fixing engines, fixing the lawnmowers, and my dad actually put me in charge of like all the lawn equipment's yours. You gotta keep it running, change the oil, get all those sorts of things.
And got into that as early on. Now, obviously I was on a college career track in high school, not a vocational, but I was able to still do both. But I loved the engineering side of it. And so I really fell in love with engineering in college. I'd actually gone to the Merchant Marine Academy. And so I was gonna go be a Navy engineer there and fell in love with big engines, and just to put it into perspective for those of you that know engines, this, and I'll hold it up, was a piece of the piston ring of one of the engines that I was actually on. So it's a 1.2 meter bore by two-meter stroke. It's about 28,000 horsepower. It's a two-stroke diesel. So it's supercharged and turbocharged. That's what I was cutting my teeth on, being able to just run those kind of ships and understand the heavy industry piece of it.
Life threw me a few curve balls. So when I got out, I said, okay, let's go back to my original love. I grew up in NASCAR country, but I actually fell in love with Le Mans Formula One. So we were the odd kids on the street, watching 24 hours of Le Mans all the way through the night. And my dad's inspiration for that continued to feed into maybe I should go do this. And so I up sticks and moved to England and went to Oxford Brooks University.
So there in Oxford, absolutely loved it. And my first winter was at Williams F1. They were actually sponsoring us for our Formula Student Car. So we're building and doing all the carbon layup for our formula student car. It was a carbon tub right next to the FW26, which was the elephant tusk year for Williams. And so I thought, okay, I think I've made a good decision here. My internship year, I was worked for a mom and pop shop out in the middle of nowhere, England, doing historic F1. And so everything from a Coventry climax from the 50s all the way through to the Matra V12, my favorite. It was actually voted the best sounding engine of all time, the Matra V12. You should look it up. It's beautiful. I got cool pictures about it as well. All the way through to the late 90s and early 2000s V10s, F1. So being able to see, because I learned with my hands, being able to see what was the idea then, what were you allowed to do, what was the design of the time and watching it morph and change over 50 years. That was it, it just furthered my passion even more. The year I graduated Oxford was the year they froze all the engine rules in F1. Very sad. Fat chance of getting the F1 job. But I ended up working for Jaguar Land Rover. And even though I moved from like well I'm gonna go play with race cars to working on SUVs, the level of complexity that we had in those engines was my real test as a junior engineer.
Now being able to look at a multi-degree of freedom engine. We had 16 degrees of freedom, right? If you think about it. And those of you who are engineers and understand what that means, visually we can talk about three degrees of freedom, right? 16. Turns your head inside out. So now how do you deal with such a high level of complexity? And instead of just getting swimming in data. Right, we would generate anywhere from a terabyte to two terabytes of data a day. And just getting data input and for what we were doing from an engine mapping standpoint and things like this. How do you sift all that data out and really start to build out smart ways of accelerating your data output so that you knew, okay, I know where I want to go, I know what I want to look for. I need to get the minimum number of data points possible to build out this output. And so for those that are not used to this field, we call it design of experiments. For those of it that live in this field, be pfft, Scott, that's small beer. But mind you, this was 2006. This was 2007. So that kind of mindset wasn't really into play yet. Everything had an engine map, right? No, we're now starting to talk about models. We're now starting to talk about getting absolutely everything we needed and not measure it all. So working on that, that got me still into motorsport. So I was able to do a 24 hour jag at the Nerbergring and do the diesel. So I was the
Daniel
That's so cool.
Scott Davies
It was such a cool, well it was fun though. So if you ever, those of you that don't know, everybody knows about the Nürburgring, those of us that are car guys, but they do the entire circuit, not just the GP circuit and the Nordschleife, but the whole thing. And it's 24 hours. And it's VLN. I can't remember the name off Deutsch, but it's basically a hundred and eighty-car, one eight zero, number of cars in the race. They actually start it in four sections and it's the full 24 hours. So we did a 24 hour jag with a diesel. And the whole joke was to do it that it's a jag. It's a jag, right? If you say like Jeremy Clarkson does. You meant to do the whole race with your pipe and slippers, right? Because it's meant to be a comfortable jag. It's still a race car. But the nice thing was it was a real big foray into understanding that whole endurance race mindset. And as a junior engineer, I'm running the engine program, the data race program, and then I actually did the modifications to the engine. So we bumped it up another seventy horsepower, which for that engine it was right on the ragged edge. But it was great to continue to keep building that out. Well, that got me some notoriety and I got headhunted to go to McLaren. And you can imagine the phone call. And so at the time, the twelve C had just come out. It
Farbod
My God.
Scott Davies
And we can talk about it, right? 'Cause it's in the press now. But the 12C got panned in the press. The tagline was it's a supercar, but you'd never know it. It's a terrible tagline. So the leadership there said, no, we're gonna change this thing up. Let's do this things a little bit differently. And so they pivoted their recruitment strategy, they pivoted their design and ethos strategy, and so they pinned me as the opportunity to be the first in-house person to do the engine calibration and support the mechanical engine development, because they had contracted it out before. And so the 650 on through the P1, P1 GTR and all those, those were all in-house. And it was that engineering Nirvana moment. It's a clean sheet. Nobody had done it before. There was no like, well, you're just gonna inherit this process, you're gonna figure this out. Brand new. And so to be able to take it from a fairly rudimentary test house, because we were a live-in customer. Can you imagine being a live-in customer, some of your suppliers, right? Live in customer. And to be able to continue to build this up into what we turned it into, it was a two-part problem. You had to develop the supplier, develop their processes, because I need a certain quality of product output. And in respect a little bit, but at that point in time, they were just a durability house. Their past fail criteria was like, did it blow up? Yes or no? Being facetious, but that was their level of expectation. It's like, no. I'm coming from my 16 degree of lifestyle of being able to get whatever data I wanted at whatever time. And so to teach them to say I need one percent accuracy across the entire range of my entire test regime or program, they couldn't even reach the top speed of the engine. It's like, no, sorry, we can only map up to six thousand RPM. And I have to go up to eight, five.
So you develop supplier to develop their mindset. You encourage them. You helped build them up. It's like, no, this can be done. Let's be creative. And my time out at sea drove that in to say you work with what you have. Right. We used to say any old donut can ask for the moon. And like, no, pass it here. Everybody else is telling me, no, you can't do it. So this encouragement mindset I saw lead into who I became as an engineer and then eventually the engineering leader. So myself, I got to hire a few people in, gave them that leg up opportunity. And we really became the super powerhouse where we could take and land somewhere with a supplier, develop them, develop their processes, then develop what we're supposed to be doing. By the way, Scott, you're still supposed to be developing the engine. And it just became this great opportunity to be able to understand what the supplier goes through, to understand the data onslaught and to understand that we were a remote office.
We were literally sight unseen. And the big mothership was down in Woking, but we had our little Skunkworks place up at Milton Keynes. And it allowed us to become our own mini business. Fair enough, we're under the umbrella of McLaren. But I had my own supply chain. I had my own development part numbering system, still feeding into what the official part numbering system was that we needed for the road cars.
But what was a nice treat, what came out of it was, fair enough, we're doing the road cars, but it got to the point where the motorsport program, the GT three and the GT four program, needed a shot in the arm. And as this continuing to bring it in-house mindset came through, they said, Hey, Scott, we need somebody to run the power chain program for the GT three and the GT four program. And I looked at the guys, we actually went out to dinner one night, I learned the Italian way of looking after my team. We went out to dinner one night and we sat and literally, okay guys, go no go. It's that Apollo thirteen moment. I'm Gene Kant sit there at top. Go no go for launch. Go, no go, go. And we all unanimously looked at each other and said, look, what's the actual uplift of what it is to get that done? It's like, well, our standard of what we've built and what we've put in place exceeds what the actual motorsport guys actually need. And we actually have to get rid of two hundred horsepower to make the engine legal to race. You're like, is that a thing? Right.
Daniel
It's good position to be in.
Scott Davies
And so, but it got to the point where we recognized that because of the factory that we had made, I had incorporated because when I took it on, the engines were built in one place, taken apart in another, tested in another, and the forensics were done somewhere else. Four different places. So we had the opportunity to consolidate that to where we were all sitting in one house. I had the mech dev guys sitting next to the software guys, which were on the floor above from where the engines are being built and taken apart so that the software guys, like, hey, you designed this new software, you blew it up yesterday. Do you want to come see what your software did? They then understand, because I had junior guys coming through. And so being able to have that synaptic connection for them was pivotal. We went from like, well, we're not sure what we're doing, within a few months of like, we know what we're doing. We know what we're doing. And that
Daniel
Well, I can see the parallels to what you're working on today and trying to digitally connect people. You did it by literally putting them in the same building.
Scott Davies
Correct. And so this is the part that we've learned. And so when I did my master's degree, I on purpose focused on the global business mindset. How do you continue to foster this creativity and teamwork when you might never meet them? They're 13 hours time difference from you. They live in an entirely foreign country, you might have the language barrier.
And to give you context, my office, okay, we were all local there and spoke English, but our parent office there back in Woking in the power training department, 17 languages were spoken just in one office. And so now how do you build that latitude where you give those people this, you don't try and step over them or don't try and talk over them or try and correct them? Let them get the words out. Let's build that relationship and communication. So seeing what the in-person shoulder to shoulder teamwork mindset was for what we had built and then being able to say can you, could you, should you, you want to ask, should you be able to continue to try to build this global mindset. Well, what came out of my classes and what came out of my learning in application was that you really had to have a very robust means of connecting people. You had to have that infrastructure and it was actually part of our studies to say watch this when you don't have a great communication system or an ineffectual means of communication. It could be the person, could be the leader, could be the infrastructure, and watch it fall apart. And so we do these scenarios and case studies and stuff to try and play that out. So this was that, okay, I have my experiment, I have my hypothesis, I have my experiment now, and now I just need to run my lab. So by that point, I'd been at McLaren six and a half years working a lot of hours. I ended up having three kids through that. I had one just before and then so I had four kids by that point. Dad time is starting to take its priority, I think, over my ninety hour work week. And so there was an opportunity, I got headhunted again, to move back to the States. And this was six months before the pandemic broke out. So we upstixed and moved to Minnesota. Never lived here before in my life.
Actually drove through here in a development vehicle in a Land Rover years before. But I said, okay, let's try it. I kind of know what it's gonna be like up here. And so landing here, I was able to work for a company here based out of Minnesota. And I was able to learn and apply some of these leadership studies and principles that I'd seen of the corporate dynamics, being able to apply this infrastructure theory that I had put together.
And my team, I had four separate groups underneath me, spanning again, four countries, and one of the teams I never got a chance to meet in person. It was always virtual. So how do you continue to foster and build this camaraderie and that piece of it? But we're still developing discrete products. How do you ensure that that actually plays into it as well? And I was actually a PTC user at that point, fair enough, at a director level.
But I was seeing my team collaborate and work together and seeing this infrastructure piece. And this was that epiphany moment to say, sure enough, my team is joined at the hip, despite the geographic difference, and being able to see that we're able to move. So a hundred percent, there was four different business units, but a hundred percent of all the four different business units, which were very different, discrete products, all a hundred percent came through my team. And so to have that different mindset. You literally, and we used to joke about, you'd have to take the hat off, put the other hat on to talk to this team, to then take it off and go put another hat on. And so to be able to deal with the variability that what we would get as a central unit spread across that group to then be able to say, sure enough, we've got to work through it with them, that was what we were seeing as a big success. And this is what led me to where I am now, being able to recognize, okay, I'm still able to continue this hypothesis and this lab and what I'm seeing now through the number of different people that I speak with, how they're going through similar challenges, similar battles. And one of the reasons I got headhunted to come to Minnesota, they had some of the same suppliers, the same problems in a powertrain mindset. I was like, guys, I've been here, I've done this, I know how to work this out, even though the engines were significantly smaller.
So it's fun now to be able to sit in this seat and to be able to help so many different people across the board, whether it's automotive, airspace and defense, and then even into the industrials side of things. We could talk about plastic bottles, could talk about tanks, could talk about engines and race cars. The concepts and some of the things that the companies struggle with are the same, and not to diminish their struggles, but there's a means of being able to encourage them. And walk them through what it would look like to get them out of the mire, I R E, right? They're weighed down with a process, they're weighed down with something that just seems to take forever. And us engineers, I got a chance to work with a lot of the Oxford intellectuals, right, when I was there. And one of them, one of the philosopher types, he's like, You engineers, you're actually the same as artists, as creatives. And of course that caught my attention. So calling me a Da Vinci kind of thing. It's no, more like a Michelangelo.
Farbod
Say more!
Scott Davies
Right. Exactly. So but you go back and look at this creative personality and his comment to me, which I've quoted to just about everybody, we are artists that just chose, I'll say, a peculiar medium. And I say a peculiar medium because most artists are like, you paint, do you sculpt, do you pencil draw?
No, us engineers, our creativity comes out of this necessity to solve the problem. How creative are you going to be to solve the problem? And if you go back and look at how we're driven as engineers, we want to have this freedom to create without this constraint. So are you my numbers guy? Are you gonna be my design guy? As a team, are you collectively solving these problems or wanting to change the world through the discrete products that you make? And this is what really spurs me on, coming back to close the loop on the point, is that when I recognize the groups that I speak with, those engineers, you can hear the lament in their voice centered around, I know what I need to do, I know what I want to do, but I'm forced to use this process. And you go, and they're smart enough. A lot of them are smart enough to go, this is 70 mouse clicks too many. Can we change it please? Or I'm forced to do this email, which turns it into a PowerPoint, which turns it into a Word doc to do this thing just so I can have this chat to just, can I design the piece please? And
Farbod
That's one of the things I really appreciate about you saying Michelangelo, 'cause I think he was the one that famously said, I saw the figure and the marble and I carved it away until it was free. And that's such a parallel with the engineering aspect of, I saw the issues and I'm carving away at all the fat until we get to where we need to be.
Scott Davies
And so many people have explained that to me as well as, Scott, and other engineers that I've spoken with, you guys see what none of us see. I look at it and it's like I just see a big giant piece of marble or a problem. And they can't see past the problem. And you can hear it, you can see it in their voice. You go, wow, no, you really don't see it. Now we can't be condescending because that's rude, right? As engineers. But what is our job is to be the translators now into what do I see and how are we going to get there and what is it going to look like. And to be able to pull all of this together, this is now where what I saw in my own experience with my team at McLaren is the second you can inspire them to say you have autonomy, constrained autonomy, but if you have autonomy now to go really truly make this happen, this is where the acceleration happened. And this is what I'm able to encourage to all these other new clients that I speak with through PTC, is to be able to give them that encouragement. It's not just boilerplate discussion anymore. There's credibility to come into what we're talking about. And when you have this autonomy and this freedom to create, PTC, the new logo name owners power to create, but there's a means to be able to empower them. And so be able to have this, I'll say, free reign on the creativity without the constraint of some yesteryear process or yesteryear tool or things like this. This is now where we're seeing the feedback from who we talk to, it really starts to amplify and it's a compounding return. And this is the part that we saw that when I was at McLaren, it looked a little rough at first, it was a very humble beginning. My office literally was a broom closet. But to see it turn into what this acceleration case was where we could take something, and we talked about it in the beginning, I know, but the Senna, to go from clean sheet to car within just a few months. Well, how do you do that? Right. And how do you turn something that was entirely different? And you'd say, well, is it just a variation on a theme? No for us, because the nature of what we did and some of the commodities that we were working on, it was a clean sheet. You really had to start from like, I can't use that and I can't use that and I can't use that. So I have to start from the beginning and try and make this bit happen. And so the creativity piece, being able to give them platform than the engineers now. The people in those engineering fields, all they really want to do is just be creative, solve the problems and continue to go faster. But you got to be brave to ask that question though as well. Do you want to go fast? How fast do you want to go? And I asked that question a lot now. And you can see the people just respond oddly for a second and go, well nobody's ever asked me that question before. It's like great. I'm glad I'm the first one to have asked you that question because it's not a conversation that regularly comes up. We need to keep going, we need to keep improving, we need to improve our credibility. Instead of asking, well, how fast do you want to go? And so a lot of people will end up seeing the Michelangelo example. They just see the marble, they just see the block. They don't see what it could be. And so this is the part that I've taken from my experience and continue to keep applying even today, being able to help them along at how fast do they want to go.
Farbod
That's been one of the things that's been stuck in my mind since we first chatted and then I went through your LinkedIn, is how did you know to be the kind of engineer you are? Even going back to your first professional experience at Jaguar Line Rover, that is not the common output I would expect from someone fresh out of college doing their first job. You said it yourself, you accomplished a great deal. That made you be headhunted by McLaren. But it seems like you were thinking one or two steps ahead outside of just my cat design, you were thinking about the wider manufacturing implications of like, is my supplier gonna be able to do it the right way? And if not, how do I make them do it the right way? Was that instilled in you at your university, or is it something you picked up from a mentor, or was Jaguar Land Rover really state of the art and you learned that process and carried it with you? How did you build that?
Scott Davies
I talked about my dad a little bit in the beginning, but it's my grandmother as well. She's a big music person. She's not an engineer. Cute petite little thing. Just all but has taught piano her whole life. And there's always been this pursuit of excellence. And she's always spurred us on, always, my brothers and I. And to give you context, I was at McLaren, my youngest brother was a blue angel for three years in an F eighteen pilot. My middle brother is Mr. Motorsport through Porsche down in Texas. So this is who we are. We're naturally driven to not be satisfied with just like, well, this is how it is. My dad inspired us early on, and you can tell it came from my grandmother, his mom, right? That whole vein of, can you make it better? And not to be so critical about it. It's not a critical approach. It's a well done, good job. You did great. But next time, can we go faster? And I think that was where the natural fit came in with McLaren because everybody asked that of everybody, of each other. And that was one of the things that I took away as, even, my joke was, but I actually asked him one day, you go to the janitor, the guy who's cleaning the floors at McLaren. And it's like, what's your role here? He says, My role here is to be able to make sure that this place is clean so you guys can focus on making the cars faster. He knew his role all the way through to what the actual net outcome is of the business. Right. And so how do you inspire those to one another? So that's, I think, where my pursuit of excellence came from, the practicality of the pursuit of excellence. My time out at sea, I spent my time in the North Atlantic before, which I think is why I fell in love with wanting to go to England. I actually went to England quite a lot there on my ship. And there's this case, that's why I'd said earlier any donut can ask for the moon. We have a bit more of a colorful language there in England to say it, but any donut can ask for the moon. But when you are stuck with your paper clip and rubber band and a stick of chewing gum, your Ben Gyra moment comes out. And I think that's where the compounding effort of wanting to rise to the challenge and that pursuit of excellence piece of it, it's almost like a bragging rights story. Everyone looks at it from the outside, man, that looked like it was such a well old machine. And we're going, No, it wasn't. Not at all.
And that's the part where you talk about engineers going to the bar afterwards and having a chat about what was their challenge, what was their triumph. And it was almost a triumph in spite of the odds. And that was the part that I was seeing kindred spirits there, because we were all having our own struggles, our own battles with trying to get things done. And it wasn't, we'd trying to make it complicated, it just showed up complicated. If you think of chaos theory or Newton's second law. To get things going, you've really got to try and put some energy into it just to get it going. And we enjoyed that. And so my pursuit of wanting to continue to keep pushing, I think, is, I don't know, maybe I answer long way of answering the question. But
Farbod
No, that's the perfect answer. That's exactly what I was going for. And to build on it, what I was gonna ask is Daniel has shared some of your pains from his background in automotive, working with suppliers and explaining to them that, like you were saying, it didn't blow up isn't good enough. Meeting the six thousand RPM spec isn't good enough. Let's get to eighty five hundred, right? It's easy, I feel like, to share that idea for excellence with kindred spirits, but how do you get other people to buy in that are really set in their ways and might not be so eager to believe what you want to believe?
Scott Davies
I'm glad you asked this because this was that pivotal moment that I found, because they had a contractor there when I first joined at the test house at McLaren. I won't name him. He's a great guy, but he, in my mind, would be a little provocative here, he represented a traditional customer supplier relationship. Go get it fixed. You figure it out. It's on you. I won it yesterday. Off you go.
You immediately present this conflict and this detraction to any sort of real progress, because we're gonna stand on ceremony here, I would in England. We're gonna stand on ceremony here. You have your job and I have my job. Off you go. Be quick about it.
And I think spending time out at sea on a ship, I had two ships nearly sink out from underneath me. That's a funny story. But when you find that there's no time for ceremony, there's no time for this positional jostling of like, well, I'm the boss here and you're the, no. All of a sudden when you have this emergency crisis, and I say the sinking ship thing on purpose, never will you find a more cooperative team because your life depends on it. Everyone works shoulder to shoulder at this point.
And it takes some emotional intelligence, I'll admit. But when you have the ability to be able to work with your supplier and to be able to put it into a position where it benefits them and to be able to highlight the benefits, the value to them. Hey, look, we're gonna do this thing together and I'm gonna teach you how to do this and you're gonna work with me because ultimately I need it. But because you worked with me on this, you now have a platform to be able to go have other customers show that, sure enough. 2013, when we first started, to 2015, by the time we had our system and process in place, we helped them set their standard to where the international parent company of that test house, their CEOs were showing up saying, Look at the change. Where did this come from? Because we were teaching them how to do that. We gave them value on understanding, we might be the awkward uncle that can't seem to get out of the basement, right? We're the live in uncle.
But yet we saw their good days, we saw their bad days. And being able to map out how do we work this together, the net result of being able to have that improved customer supplier relationship, fair enough. We were there with them. But it meant that what we're doing as a starting point, when we start to have the discussion, when we start to pull them in, being able to recognize that value up front. Yes, legally and contractually, we have to have all these binding and bounding contracts to protect one another. But when the mindset is right and they recognize, this is not going to be combative and we have a means of being able to work together. This was one of the main ingredients that we were able to pull together and see this acceleration piece really truly come in, which I was proud of. We had a great working relationship. And I mentioned the contractor before, where I showed up to a very hostile environment. They didn't want to talk to me because I represented the enemy. And it took me a good couple of months, but we finally won them over to recognize I'm not here to criticize. I'm not here to condone. We're gonna have our good days and bad days. And sure enough, we set the fire alarm off at least once a week. Those early, I'm serious. Regularly in English winters, you do not want to be standing outside in January because Scott over there set the fire alarm off. And just, that's the nature of testing and development, right? For those of you listening on the podcast, you know what I'm talking about. You gotta keep pushing until it breaks. But when they recognize this is just a matter of course of the day. They came alongside us. They started providing solutions and suggestions and alternatives 'cause I don't have all the answers. And this is where collectively we really started to accelerate our work and relationship with them. So
Daniel
Got a bit of a rabbit hole if you're willing to venture down it with me. Have you seen the movie Inglorious Bastards?
Scott Davies
I love that movie.
Daniel
Okay, so you know the scene where Hans Landa is interrogating them about the three that they hang up because they did the three this way instead of this way. I had a Inglorious Bastard's Three Fingers moment when you, can you tell all of us how you properly pronounce the J in JLR? It's not Jaguar.
Scott Davies
Jaguar.
Daniel
Jaguar. Sorry for the aside there, but it's been sticking in my head. He doesn't call it Jaguar, he calls it Jaguar.
Scott Davies
Jaguar. And I was corrected. That was a thing as well. I learned to blend in a bit better. And living where I did in Birmingham, and in the surrounding areas, particularly during my internship year, we're both speaking English, but you would never know the difference. And so I learned to blend in as best I could, but to learn a proper Brummy accent and everything else was well. But to work at Jaguar Land Rover, if you didn't pronounce Jaguar properly, you were tossed on your ears. So no, and I smile politely when people call it Jaguar or whatever else. So but no, it's Jaguar. It's Jaguar.
Daniel
That's your authentication check right there. I've worked with some folks that worked at JLR and I've gotten a tough time for calling it Jaguar or Jaguar, so I know you're legitimate in one second right there when you say it the right way.
This is awesome. Well, Scott, I think another thing that might bridge us a little bit more to the work you're talking about or the work you're working on today is, I Farbod, mentioned LinkedIn earlier. I also checked our LinkedIn connections and I've had the pleasure of working with a lot of people that I believe you've worked with in the past before at McLaren. One of those guys being an absolute wizard of an engineer, who is Andy Jones. And
Scott Davies
Yeah. I love Andy Johns.
Daniel
My whole experience working with Andy Jones was entirely remote. He was completely in the UK the entire time we worked. I was here in the US the entire time we worked. Not only was he responsible for being a wizard of engineer, he was responsible for, as a director of advanced projects. So he was working on structures for new things and how are the engineering team that's implementing that supposed to interact with the person who's working on the advanced new concepts if they never see each other face to face, if they never stand around the same buck and point at it and can talk about let's do this instead of that, or never even just sit face to face and have a discussion on the same whiteboard about what's going on. How does technology tools, how do you bridge a lot of that connectivity that you've felt at different points in your career being face to face with engineers, being in the same building with the other engineers and other customers in the business you're working with, even going in living in with your supplier and building a real relationship there face to face on how those relationships can be developed.
What tools do we have in the global engineering economy that we have today where people are all over the place and your suppliers are all over the place and the logistics people are all over the place and the assembly plant, there may be several different assembly plants consuming the same parts. How does someone get closer and closer to that rapid development like you guys had on McLaren Senna? How does someone get closer and closer to that while also dealing with the challenge that they are physically disconnected from one another? What are the digital, you call it digital thread, but what's the connectivity look like to help get people on the same page? Does that look like just a really beefy system of record or are there other intentional ways that people can interact with one another and organize their teams to make it more effective?
Scott Davies
So if you look at the root cause, the root problem of what generates the friction when you have a geographically separated organization, is the data ready to hand. Why do leaders conglomerate and say, Well, I did it too, right? Hey, we don't have the infrastructure in place. So my default is to put all of you guys together in one room because that's the only way we're gonna get this thing done.
So if you look at the expediency quotient, I'll call it that. I've just coined that just today, by the way. If you look at the expediency quotient, you've got your factory leader, you've got your tool maker, you've got even the leader who's like, Well, what's occurring today? How fast can you get the data? What is it what they need? Are they even allowed to see it? That's a whole other story. But if you go back and look at that, there's a common thread there that when you have the right kind of infrastructure in place, and you make the data present, not to present them to them, but that the data is present as if they were there, that's where that expediency quotient starts to come in to say you now have the right sort of ingredients to go as fast as you want, because you've thwarted the geographic distance. And this is where that master's degree class I was talking about came in, to be able to say, what do you do to collapse the time zone difference? What do you do to collapse that? Now, aside from getting up at three in the morning so I can go talk to Japan. In England we were very serious about our antisocial hours. So what do you do to turn the problem on its head to say you can't have a meeting anymore? Now surely you can. A lot of leaders have to do that these days, but as soon as you remove that out. You can't do this as a function of a meeting anymore. Right. All the transfer function guys are going, okay, that's now out of the equation. I gotta go back and make up a new transfer function. Now you have another means, another avenue to say, well, okay, fine. What was the root cause of the meeting? Well, I needed to make a decision on this point. Cool. Well, let's just jump and shortcut to that. This is where having that right sort of infrastructure comes in place with the right sort of access. And this is where we get the IT people all up in arms. I don't want, make access for everybody. But this is what we had, our way of doing this. And to give you an example of what I see as a successful data access, data outcome, we had one of our first engines, it was one of the new programs, testing over Christmas. Right? Christmas, we're all gone, we're all at home. But we had set the infrastructure up in place.
I'm there with my kids. It's a beautiful Christmas morning. I get the phone call Christmas afternoon. Hey, we've had an incident. Okay. And I know what engine it is. I know what the program is because I was only running one over that time. Within 40 minutes, none of us darkened the door back in the office. All of my team and remote people in Spain and Germany, all collectively within 40 minutes, and Italy, because they were in Italy as well. We were looking at the data. We could see the actual video of what happened, because we'd put the cameras and stuff in place. We had the data access and we were sitting there and we did a forensic analysis without even darkening the door to be able to say, We know what happened. We know that in this particular story, the operator had turned off the alarm. He knew this engine was dying four hours earlier.
We had more than enough time to stop and put protections in place, or at least we had an engine that still worked before it decided to have all the insides be on the outside. But if there's a recipe for success, when you have the right infrastructure in place, this is a successful outcome. It's a shame the engine died. But it actually found further cases that all the systems that we'd put in place, some of it didn't work because there was some sequence of turning the fans off and this or whatever. We had to have these other issues come in. So that's a recipe for success when you have that expediency quotient where you've got a means to be able to get to the data right now, look at what I need. I didn't want everybody having access. We were the only ones that had access to that. So when you can do that with your supplier, when you can do that with your peers and have that ability to bridge the gap. And so playing this out when I was at my company here in Minnesota, I had my Indian team, right? They were based in Bangalore and they were a brilliant team. And the nice thing was we could work 24 hours around the clock effectively. They're working in their time frame. I'm working in my time frame. And they were able to do some work and they would get it set up so that we would have review in the morning. So I could literally sit here with my coffee and go through and have a look at all the things they had worked on the night before, waiting for approvals, looking at this, whatever. No meetings. No PowerPoints, no Excel documents, no, I need you to review this and sign the bottom. We were looking at the actual end data, the end widget pieces of what we were doing from either design decision, design review, those sorts of things. And when you have that sort of right infrastructure in place, that's where you start to see this collapse in time play into this expediency quotient part of as well. Does that make sense?
Daniel
Yeah, it definitely does. And I really relate to the foundational element of all of this, which is, is data in a good enough position that you can actually trust someone else to pick up where you left off. If that isn't in a position where you can do that, you can't do anything else, which is kind of crazy. It's like the linchpin holding that entire complex system together.
Scott Davies
Right. And there's something to be said there, because you'd helped touch on it for a second. A lot of people will say, Well, we have to document this. And you have to be brave enough to ask, why? Why are we documenting this? Well, the government says so. Okay, cool, fine. Well, the government says we have to do that, great. But for the rest of it, you're like, Why are we doing this? Well, I was told to do this. Well, we've always done it. And you have to have that bravery within the organization. And that's, I think, maybe the role that I play sometimes in my current role now when I talk to other clients, is to challenge the premise, not disrespectfully, right? Not trying to get people upset or fired. But to come back and say, is this value added? Is this actually helping us move the ball down the field? Is this actually helping us make sure that we have thorough documentation, but not a document for document's sake? And it's a really provocative, some people, it's a really provocative question. And their immediate response is, well, how dare you, sir? Right? This is what we do.
But you have to have that emotional intelligence enough to be able to challenge respectfully, but still come back and say, look at who we are as a business. Can we go faster? Should we go faster? Are there things that we can look at? And then you say, well, we still need the content of the document. Great. I don't disagree. But does it need to be in that medium? Does it need to be in that format? Can we find some other way and some other method to still get those decisions and the traceability on those decisions so that we can really truly go faster?
And that's the part where I've been in big rooms where I'm talking to 20 people at a time, and you can see the collective light bulbs pop up all over their heads to go, huh? I don't need to do this anymore. And my job is done. Thanks very much. And it's not to say that we see the process get obliterated or die, but we start now have this different viewpoint where we collectively start to look at this process. And this is what we did at my team at McLaren. Fair enough, a much smaller team. But we would have a Friday, we call it our Friday afternoon cleanup. And it wasn't just to clean up the shop, but we would go back through and, because England, right? We love our banter. The banter in the office was next level. Probably would never want to repeat half the stuff we said, but we had a great dynamic, a great working relationship, and a good relationship enough where we could challenge each other. Hey, I saw you working on this. You sure that's really what we want to do? Can we go faster? And we'd continually challenge each other. And you'd see this tit for tat where you genuinely see a really good healthy outcome. And this is where we would, because we're all racers at heart, the guys that are McLaren. And I say that it's not just a McLaren mindset. I've seen it show up in so many other clients that I talk to that it really truly does show up elsewhere. And it's just a case of just being the catalyst, just being, I'm the guy that lit the match and watch the rest of it start to happen. So yeah, I don't know. Long winded answer for that, but you got me triggered on the document piece of it. And I think that's another ingredient for what really can make people go faster.
Farbod
Scott, I couldn't forgive myself if I didn't dig deeper into the Senna, being the McLaren fan I am, but as you were talking, I was curious. The Senna was completed in a remarkable short amount of time, from idea to what ended up hitting the road. How much of that was what you were just explaining, which is just pushing back on processes, really peeling back what is needed, what is not, versus leveraging technology?
Scott Davies
A bit of both, to be honest. So some people would say that we rated the parts bin. Some people say that, my favorite analogy was Mr. Potato Head, right? Take out the happy eyes, put in the angry eyes. Hey, look, it's a new Mr. Potato Head. Is it? There was a ton of things that we did because we had some operational targets. The design and the bodywork and the vehicle and some of the arrow stuff that they did. Andy Jones and the guys on that side of the business from the vehicle side, they had their targets to holistically move the car into a much more of aggressive position than what the previous ones have been. But our target, and just to put it into perspective, in 2013 we had the 650 and the P1. We were told to increase the power output and the durability collectively. Power output had to go up by almost, do the math in my head, thirty five percent. Thirty five percent power output, and we had to an order of magnitude increase the durability.
And those of you guys that are doing the numbers in your head from a powertrain standpoint, you're like, So what did we change there? What did we do? And we left no stone unturned. New head design, new planum design, new injector design, and then for what we were able to do with our turbochargers and some of the other arrangements, there was an ability to be able to take the process. And this is what we have been quietly building up from an infrastructure standpoint for a long time, to be able to Mr. Potato Head the engine. There are things that like, well, look, we don't need to worry about that. That's developed, that's designed, that's done. It is part of the whole system now. We still have to validate the whole system, but we didn't have to redo every single thing. And there was a lot of the processes that had been given to us by our suppliers to say, you change one thing, you got to go test it all. It's like, well, that's gonna be another 18 months worth of testing. For what? It's like, well, that's our process. That's what we do. It's like not today.
I've got data to prove. This is where I was talking about my 40 minute engine story. We've got data to prove these components that we know that we're not changing. We're literally applying them to the system. I don't need to test them anymore individually. We can test them as a whole at the end and we'll go do that. But for all these other interactions, all these other developments, we looked at the process and we looked at some of the technology that we were able to deal with either from the data management or the physical testing itself, to be able to say, I know how to compartmentalize each of these areas and to be able to say, all right, we have traceability now. We have traceability to show that because I have all my data, this is a validated piece that I'm plugging in. If we have a failure, it's the failure at the system level that we need to go back and look and redesign or develop. It's not going to be the individuals. And you say, Well, how do you know? Well, I'm standing on 10 tons of data.
And so there's pieces there that, that's where the part of the process was coming in. And that's what our ethos was, if we're truly a supercar company and a supercar mindset, everything should be going faster. And so no stone was left unturned. So even to the point where the supplier is telling us for us to sign the document to say that we're gonna allow to send you the four hundred parts that we decided to send you, for because we only made so many centas, right? So we're gonna send you some, there's things there that we had to challenge to be able to say, this is our approach, this is how we're gonna do it. And it really challenged us because we ended up finding we reached the leading bleeding edge of the process development, but also the component development as well. And so again, we moved out of the supplier development now because I had a stable supplier base, from a testing house development, from our supply chain and others, that was stable, which meant we now, and this is the part of what we talk about at PTC, this engineering capacity bandwidth. I'm not having to deal with the minutiae every day that I can't seem to get a break or get a breath for a second. And now I can go, okay, well that's done. I can now look up and I go, I'm gonna go attack this. I'm gonna go attack this. And it was a compounding cycle. And so being able to continue to develop the process, which is where a lot of our time savings came from, the concept of engine mapping and development and system integration and system testing and vehicle testing looked kind of the same.
But because we were able to have the traceability and validate to show, sure enough, I don't have to test it all and turn it into a 36 month program. We were able to show validation and cases for it. And our defining moment, and I think this was what was really happy about it. And I know back then, the 12C and stuff, they were a fantastic car, but could you do a 24 hour race in them? There's some people that would say, we're not sure. We're not sure. And this was our challenge. This was our internal challenge back to us. Our chief engine designer, who's still a great friend of mine now. He's at Honda doing their IndyCar program. But if he's the mechanical side, I was the software and the system integration side, and the two of us working together, we'd come up with some pretty wild stuff. He said, let's do a double LAMA. I want to see this thing go Laman for forty eight hours.
It's like, all right, sure. So we've got a means of being able to do testing like that. And so we ended up putting the whole system into play and ran the Nerbergring. Never mind Lamal. Said, no, put it on the Nerbigring. Let's do the Nerbigring. So we did the Nerbergring and by hour fifty seven, it was starting to show signs of, okay, she's starting to get a little weak here. And we can see the data, we can start to see that okay, it's starting to get a little tired. So we said, okay, we'll stop it at hour fifty-seven. We reached the pinnacle. We actually got a cool picture of us as a team showing that picture. And you think from a timeline from 2013, no processes, no internals, we had been relying on the suppliers to some in-house stuff that what we were doing in my team still had a great supply chain. That was twenty sixteen. And so to be able to show a picture that say that here's the engine that did fifty seven hours of the Nobergream. And the team that developed, and we had a cool picture of us with the car. That's what we did. That was our approach to saying, we're gonna look at everything. You can't look at everything all at once. You have to build that up. And so being able to have that logical process of build my infrastructure, have that strong infrastructure, the great data supply, data content, the right kind of data that we're looking for, now gives you this engineering capacity. You're paying your creatives to do something creative. Let's go for it. Where are you gonna get the value out of being able to pay these creatives to solve all these other problems that we had talked about? And this is what we were seeing come through. And so now my lab, being able to talk to all these other customers and clients, being able to walk them through the same sort of thing as they go through their journey of how do we go faster.
Daniel
Think for people coming from a background where I've also been on an engineering program for something as complex as an automotive that made it from idea to production in under two years. You just dropped some really important notes there that people should take notes on if they're trying to follow suit, mainly around validation. Validation timelines are things that people just assume are set in stone and because the person who's running tests is smarter than they are, they assume that's where the time is stuck. But having a solid conversation around first principles and understanding where risk can be taken and where risk shouldn't be taken in terms of validating things that, safety standards are very strict on a car. Understanding and questioning where risk can be taken and where you can catch back up by validating at a system level as opposed to a component level and stuff like that, understanding where there's redundancy and using that to cut time out. Scott, you just dropped some gems for people who are trying to do things quickly in complex development programs, for both and myself included in our day jobs.
Scott Davies
Yeah. Well, here's just a little nugget here as well, because you touched on it. I'm gonna mention it just for a second. I learned this my brief time in the military, and then I've had a chance to work with a lot of different military people over my career. And it's the junior officer problem. And you talk to any military person, they'll recognize this straight away. You've got a guy fresh out of school. I got my rank, don't you know? You gotta salute me. And he's got his chief master sergeant or senior master sergeant or chief petty officer. Guys with a lot of experience and no degree, right? They've got that degree with experience. And what I learned taking my military mindset is to be able to show up. And here's where the emotional intelligence piece comes in. It's good advice for the junior guys. Is that chances are you'll work with that technician who's been doing this test year after year after year. He's got those cycles. He's got those developments where sure enough, they know where to make it faster. But nobody ever asks them.
Or he doesn't have the platform to present his ideas back into, hey, I think I can knock 30% out of this test. And because of just life just being hard on everybody, whatever, they never get that chance. So they figure like, well, nobody ever wants to listen. So being able to have that platform, and not to say that I'm great at this or anything, but I fostered my people to do the same. I said, you need to listen. The guy that's sitting next to you on the test bed, fair enough, this is an engine development, isn't engine validation type mindset. It can be applied anywhere. But the guy sitting next to you has got a wealth of knowledge and experience. Let him talk. Let him help develop and provide input and guidance on that. One, great motivator. Two, helps to start to give him some autonomy. And there's opportunities where you now have this great way of being able to pass on ways to make things go faster. And this is what was another aspect because the technicians that we worked with at that same test house, they had 30 something years of experience, each of them. And I went back and took a tally. I was sitting on nearly 300 years, 400 years worth of experience on what worked well and what didn't. Fair enough. Still a computer, still an engine, put a bit of fuel in, makes a bit of noise, the simplicity of it all, but there's so many little intricacies and details that we ended up redesigning our interaction with them and said, We actually have stuff to learn from you. Please tell us.
And it was another catalyst that we used into that. And so being able to have that infrastructure and platform again, where you've got a means of having what I call in this context now, my role, what I call two-way requirements. A lot of people will talk about waterfall and agile and requirements management and systems engineering and all these other pieces. And I'm an ECOSI member as well. So this is my world. And there's things here that, it comes back to that positional jostling I was talking about earlier. I'm the boss. I'm gonna tell you what to do. Off you go, be quick about it. No, check this out. The second you provide the right sort of infrastructure where you've got two way requirements, everybody thinks it's supposed meant to be perfect out the gate. And don't let perfection get in the way of good. And I don't wanna say good enough is a statement that we want to live by, but there's things here where you need to understand there's a time element to this. We're gonna get our first cut at it.
Think agile process development. We're going to get our first cut at it. We good? No, cool. Let's improve it. Let's try it again. Keep improving it. Keep improving it. Keep improving it. And so when you get this time-based element to it, what is that feedback loop? Well, the feedback loop comes from everybody. And you can imagine the poor systems engineering guy going, I got to get feedback from everybody. Are you serious? It's daunting. All of a sudden you realize I've got no way to handle this in any other traditional mindset of how do you handle those inputs? Sure enough, it doesn't work.
But when you have that right sort of infrastructure, this two-way requirements method is another major key of being able to have a really fast acceleration into how do you develop your products faster because you've got this background and experience of all your people that have been doing this for a long time within the business. You've now got a means like, well, I want to build a rocket to Mars. Scott, we make tires. Right. And I'm being facetious about the example just to drive the point home. I didn't consider, as a design engineer, what my downstream constraints are. I didn't. Is that rude of me? Maybe some people could be offended by it, but there's a means of being able to understand who am I working with and what am I working for? And what is an end goal and that end design state. And when you have that umbrella goal, that umbrella focus combined with what am I working with, right? How do I make this bit work? You've now got a means of being able to go faster because I don't spend all this entropy, good engineering term, right? All this energy with no energy conversion, a lot of energy with no conversion, right? Well, I tried and I asked and they told me no, so I'm gonna go ask again. No, don't do that. Understand your constraints and understand your requirements. But when you have that right sort of infrastructure in place, it really starts to help accelerate the outcome of that. So anyway, sorry, you got me on another tangent there thinking about it.
Farbod
I wish we could just keep going on these tangents, man. I'm loving this.
Scott Davies
Ha ha.
Farbod
I was gonna ask, we've talked about the offerings from PTC, and Daniel did a great job of inserting it at the beginning of what this offers, what the average audience member who might have never used the PLM tool before should know about it. Is there anything do you think that we missed in the conversation, especially as it relates to automotive, that our general audience, especially, in my mind, I'm actually thinking about the new grads coming out that have definitely never touched it, but they're going to very soon. That you think it's worth discussing.
Scott Davies
Sure. Yeah, well, PLM is just a piece of it. So product lifecycle management, if you think about it, it's where the products live through their development life. And a lot of people will confuse a PLM with what they call an ERP. And so in our words, the three letter acronyms, the ERP is the transactional side of it. It's been built. It's, sorry, it's been designed. It's ready to go to production. I now need to handle the commercial side of it, the logistics side of it, that PLM piece of it. But you want to take a step back further. Think of the Gantt chart style. We're moving left on the Gantt chart here. Why did we build it? Who's it for? Does it meet the customer expectation? Does it meet the requirement? And part of one of the tools and offerings that PTC offers is what we call the application lifecycle management.
And yes, a lot of people would say, well, Scott, that's for software development. Me as a systems engineer and somebody who's lived across multiple commodities, electronics, mechanical design, hydraulics, fluids, arrow, you name it, right? A vehicle, in this case in an automotive world, is a system of systems, treating everything as a subsystem. They all feed up to a collective. Some of the tool offerings like Code Beamer for what PTC provides gives us that means of being able to handle requirements management properly. And I'm actually leading a lot of internal discussions here, a little bit of a marketing teaser here, leading a lot of internal discussions on being able to educate the world on where the automotive world is going. And I'll sidebar here just for a second, the company that I worked for here, they were always worried that any kind of real systems engineering discussion meant that we were turning into an aerospace company.
And we are talking about trying to collapse out of vehicle development time. Can we get it even faster, six months, eight months, ten months? Go look at aerospace, ten years, fifteen years. It's the antithesis of going fast. It's thorough, but it's fast. It's not fast. So this is the part that everybody worries about. The second you start talking about any sort of system engineering requirements management, so that we know why we're building it, what we're building it for, who asked for it, that sort of level of driving the philosophy behind the tangibles that you're building within a PLM system, that's the part where people balk at it, like, I'm not sure about this. But if you look at where automotive is going with all the government regulations and other constraints that are starting to come into play, plus the complexity. This is not a V8 with a carburetor and a 12-volt system and seven wires anymore, right?
The level of feature complexity and function complexity and combined with the vehicle complexity itself, despite the prime movers getting simple through electrification and other things like this. We're still in this odd mix of full internal combustion, hybrids, battery electric. Then you realize what the application is. Where is it gonna go? There's so many pieces playing into just the simple design and development and delivery of a vehicle, you've got to be able to manage that now because the businesses are too cutthroat and competitive now that you cannot make a mistake. So you have to get this right first time approach. And I know another McLaren turned Rivian guy, is it okay if I name him? We can do that, right? Richard Farcar, right?
He was very adamant when he was chief engineer of Powertrain at McLaren, was like we had to drive this right first time approach. Right first time, which means coming back to the waterfall design has to be perfect the right first time out. No. Has to be correct here at production. We can have all of the development all the way back here. And as long as we understand what this looks like, so this looks right at this point, then we're good.
And I think that's the part that changes and being able to understand all this level of complexity as it pieces it together. The only way you'll be able to get it right first time, if you understand the philosophy, where it's going, some requirements, the constraints, two-way requirements, all these different pieces. And so one of the things that PTC provides through an application like Cobeamer, it's integrated back into the PLM environment so that when we're building the tangibles, you can have that philosophy moment of understanding like, does this meet the expectation? And you look at a lot of traditional PLM systems, they don't have that avenue to go, does this meet the expectations? It gives you the color, weight, size, who designed it and those sort of aspects. And they'll link back to the CAD design, but not the why, and so being able to pull that together, this is what we're seeing in industries like automotive to say, this is what we can do to make sure that you've got some confidence going forward that it'll be okay. Why? Because we have confidence that we've met the customer expectation, we met the commercial target, we met all these other aspects that play into the project management and the product development and product management of what we're making, in a means that again connects the right sort of infrastructure and data together.
And then you link that back even further than we've got the CAD package design. PTC was the first parametric modeling design package. Others have come along since then. But the link where we've talked about the digital thread now of being able to design it, why did we design it and where and how, this is what we designed, and then how we link into everybody else's systems, that's our calling card, is that we're not so exclusionary. Sorry, you have the wrong software. We don't want to talk to, it's like no. Give it here. Let's have a play. Let's see what we can do to accelerate to you. Our goal is to make people go faster. What can we do to make them go faster? Well, being exclusionary is the antithesis of that, right? So this is our MO. We like to be able to talk to people. We'd like to be able to pull them in and say, let's see what you got to work with. Let's see what we can do to make you go faster. And as long as you, the customer, are ready to go faster, we're here. We're here for it. Let's see what you go faster. We even have whole other set of offerings, even post-production side of it as well. 'Cause the real hope is that what we've seen in my own personal life as well, when you have that means of being able to connect all the data together and have means where you have that expediency ratio, right? You can really start to see that things are starting to just move faster because it doesn't represent a friction point anymore. So, but yeah, those is just touching on some of the other offerings that we do at PTC.
Farbod
I love that, man. I love the way you explained it. It's so easy to grasp onto the value add. Especially, again, I remember being a new grad, Daniel and I both studied mechanical engineering. The furthest thing from our mind was what was happening outside of the CAD program. So that's awesome. Now we're getting to the segment of the podcast which I think I love the most when it comes to interviews, which is hot takes. You're talking about the future of the automotive world. You got some hot takes to share with us?
Scott Davies
Future of the automotive world. I think we've seen, I'll be provocative here for a second. I think we've seen a retraction. I think it's been a cautionary reset a little bit. Just to give you where my associations are. I personally desperately want a Rivian. I've actually put my reserve in for a slate, right? I can do that to the shamus product plugs. I'm the engine guy. I have a V10 pickup truck. I'm still waiting to go get my V10 M5. So I live in both of these worlds. My children, at some point, I'm fully expecting that we're gonna have them drive full EVs. I'm painting a picture of confusion.
Okay. And it's not any sort of, I'm not being disrespectful at all. The world doesn't know where it wants to go. There's a plenty of clues of where we should go. And so now the world is trying to understand, like, okay, what should we be doing? And my hot take is that those that have some resilience baked into their process and their people, and those that have some vision, they're gonna stick to their guns. Mr. Toyota, he's been rather provocative in the last 18 months with some of the things that he said about the EV trend and where Toyota itself is going. Being able to have a multitude of offerings, which then compounds the complexity problem, but being able to have a multitude of offerings, build some resilience into the automotive suppliers and OEMs to be able to say whatever direction the world is going, we're gonna be okay. And that frustrates a lot of traditional OEMs because you think about the level of industrialization and tooling and like I've got these factories or we're gonna build these things. What do you mean I gotta take them down and shut them down? And I think the hot take, what's gonna come out of it is being comfortable with the variability, which now presents a new engineering problem of how do you design the 21st century factory? How do you design the 21st century industrialization process where you can Mr. Potato Head your factory? And this was one of those things that, I don't know if you guys have ever got a chance to see the video, how supercar is made. It's old now because it's got Ron Dennis in it. But one of the things that, because I've been to Castle Brum, I've been to Sally Hull at Jaguar Landover. I've been to all the factories of the company I work for here in Minnesota. There's this heavy industrialization piece of it, which suggests we're heading in this direction, and that's all we gotta say about that, which has some risk to it. Is it required? Absolutely. I don't want to discredit the amount of industrialization it takes to manufacture things, but having the bravery, I think, is probably the best way to say it, to be able to understand that you've got to have this variability while the world figures out what direction we want to go. Me as a customer at this point, recognizing I am still a car guy, very much so. I love my noise, I love my sound. I had an electric car in England. This is who I am. I recognize the world that I live in, and the world is still recognizing what direction it wants to go. And so the automotive industry, I think, has the best opportunity to truly make history here in the next five to 10 years. Why? Because if history is repeating itself, if you go back and look at turn of the century, 1900s, how many car companies were around back then? Think how many. Right? And what they did to amalgamate and turn into what the future ended up being. General Motors, why is it General Motors? Because it was the amalgamation of what, I think 15 different brands is at one point.
So there's things here that as times change and as times move, this variability of understanding what the right outcome is. One of my favorite LinkedIn advocates, he says the future is eclectic, not electric, eclectic. And I'll ride on his coattails for a second to say he's on the right track because in England we'd say horses for courses. You're not gonna have a racehorse plow your field and you certainly are not gonna run a plow horse in a race, right? So horses for courses, how do you understand the global environment, recognizing my South African customer is going to look very different to my California customer who's going to look very different to my customer in Azerbaijan. And I'm being very distanced on purpose because you go back and ask them, the end customer, what do you want out of mobility? What do you want out of transportation? Each of them are going to have a different story and a different understanding. Being able to have that customer input into your future is pivotal. If Henry Ford, his famous quote, the customers can have any color they want so long as it's black. That's not applicable anymore. Not at all. So how do you understand that that set of rules of engagement is very different now? And it takes some bravery again. The leadership's gotta wrap their head around that. So I don't know, maybe that's where the hot take wanted to go, but I know that my own research and my own input into where I do now at PTC and the customers that I talk to, you can hear that bravery start to peak now. They're ready to start to say, okay. We're having this EV retraction for a second. What do you know? Lithium's kinda hard to get. What do we do for next steps? And I'm hoping really that the next revolution of what we do from ability starts to really ramp up and start to take on maybe a bit more of a futuristic feel. Who knows? Just as long as I get to keep my V ten.
Daniel
Well, that's what I was gonna say. I love where you're headed 'cause I'm in the market for a new car right now and I keep venting to forebode that I feel like pretty much everything that's new in the market and in my price range is either functionless or soulless. And it feels like that, I look forward to a season of additional bravery, so I start to get something that at least takes one of those boxes, if not both of them, within my price range.
Scott Davies
So check this out. Another little quick side take. So my boss at McLaren, who's now my very best friend, I'm gonna name him, Davide Pizzari. He's at Lamborghini now and head of vehicle motion and engineering. He actually did his thesis on the emotional connection of the driver to the vehicle and how do you evoke, yes, right? Pivotal. How do you connect emotionally to the driver so that it becomes an entirely different next level experience. And he has this characteristic that he does. So he did driveability for Ferrari for twelve years before he came to McLaren. Name of Ferrari in the turn of the century, that's his DNA
In there, right? So this is who he is. And he and I are two brothers from another mother, same taste in music, same driving style, same approach to life. Honestly it was like, how did we meet? But this emotional connection piece cannot be diminished. If you don't have that emotional connection, it is, it's a solace thing. I might well go get on the bus. It's the same thing. And yes, EVs from a prime mover standpoint makes sense. Except for the emotional connection piece. And I'll go out on a limb to say that. And I drove an EV, right? And I've driven in a Tesla and I've driven in some really fast cars. But there's something to have all five senses be attacked. I say attacked, in a good way, to walk out of the car and you feel like I've had a moment. I've had a moment here, right? So and it's gonna be different for everybody. And so is it's your car that you take to the grocery store on a Wednesday afternoon? That's probably gonna look a little different than I'm gonna go find the twisty rose on a Sunday. And I think this is where the eclectic input comes in to quote Kelly Senekal, to say, this is where we're going with the future. And if we can understand the use cases and understand those customers, then absolutely. We're in good shape. But yes, us car guys, please, I need some emotional input into my car, please.
Farbod
Scott, you don't know this, but you just helped me out in a two week long, I won't say argument, but heated discussion with Daniel. 'Cause he's, being the logical engineer he is, he's had this spreadsheet of horsepower timed to sixty, everything. For a couple cars he's looking at and I was like, You're missing the most important column and that's vibes. What do you love being in the most? And just to give you some context on where I'm at in the spectrum, I'm test driving a Miata on Friday.
So completely not a everyday car, can barely put groceries in it, but I want to feel something and that's apparently where you gotta go. So one, thank you for that, and two, love that. We're seeing eye to eye on what's important for the automotive world.
Daniel
Last thing before we wrap, Scott, and I could actually talk all day long. Where can folks find ya? Where can they find the work that you've been working on? I think this is a good place to wrap things up, but want to give you a chance for it to do a shameless plug in case folks are interested in hearing more, Scott Davies, or seeing more about what you've been working on recently.
Scott Davies
So my digital footprint world is kind of small. I kind of done that by design with the nature of my background and experience. And some
Daniel
Sorry, don't look for Scott Davies.
Scott Davies
Yeah, don't look for Sky Day. No, I'm teasing. For what I do, for when I can plug it, I'll plug it on LinkedIn. I'm primarily on LinkedIn these days. But you can tell I love to talk about these sorts of things. And part of my role, I'm actually starting to show up on a number of different conferences and speaking engagements, and we post them on my LinkedIn and then the corporate company there at PTC. So I've got one coming up here in September, another one coming up in October. Our automotive executive exchange is our biggest one that we show up here, and that we usually hold around March. They're all based around Detroit. I've got some connections now with some clients and customers there in California. So we're gonna start to do some speaking engagements out in California.
But no, I'd love to be able to see people face to face. But LinkedIn's probably my number one post outfit out there. So that's what I do. I plug in what I need to from a PTC standpoint and then all my volunteer stuff I do outside of work gets posted on there as well. So
Daniel
Awesome. Well, we will link your LinkedIn in the show notes so folks can connect with you and see what you're up to. Scott, we've really appreciated having you on the show and having this conversation with you. And we truly, I genuinely mean it when I ask if we could have another conversation in the future and maybe have you come back and talk about whether those hot takes came true and why or why not from your position in the world of technology and development.
Scott Davies
I would love that. That'd be fantastic. Gents, it's been a really fun morning getting to talk with you guys. Thank you.
Key takeaways
- Product lifecycle management connects the people, decisions, requirements, and data behind a product from its earliest concept through production and end of life.
- Trustworthy, accessible data allows engineering teams to collaborate across countries and time zones without relying on constant meetings, presentations, and manual handoffs.
- Faster development does not mean abandoning validation. It means using traceability and existing evidence to determine what must be retested and where system-level validation is more appropriate.
- Suppliers become stronger development partners when engineering teams share their objectives, invest in their capabilities, and replace adversarial relationships with genuine collaboration.
- Engineers need autonomy and enough capacity to solve creative problems. Outdated processes and unnecessary documentation can prevent them from doing the work they were hired to do.
- Two-way requirements give designers, technicians, suppliers, and downstream teams a way to contribute their knowledge before decisions become expensive to reverse.
- Automotive companies will need flexible products and manufacturing systems that can support different propulsion technologies and customer needs as the future of mobility takes shape.
This episode was brought to you by PTC. PTC helps automotive organizations connect requirements, engineering data, product development, and lifecycle processes through a digital thread. Explore how PTC’s automotive solutions can help teams manage complexity, improve traceability, and accelerate product development.