1 00:00:07,000 --> 00:00:08,289 Evan Troxel: Welcome to the podcast. 2 00:00:08,349 --> 00:00:09,310 I'm Evan Troxel. 3 00:00:09,610 --> 00:00:13,420 I have a bit of housekeeping before I introduce today's episode. 4 00:00:13,810 --> 00:00:15,610 The TRXL podcast me. 5 00:00:15,670 --> 00:00:19,959 Well, I'm now collecting feedback, whether you have general feedback 6 00:00:19,989 --> 00:00:22,060 or episode specific feedback. 7 00:00:22,450 --> 00:00:28,550 You can click the link in the show notes, or you can head over to TRXL.co/feedback. 8 00:00:29,080 --> 00:00:32,950 It's my goal to continually progress what I'm doing, and I fully 9 00:00:32,950 --> 00:00:36,310 recognize that I'm not the only one with good ideas around here. 10 00:00:36,550 --> 00:00:40,209 So if you have something constructive that you think will help, please 11 00:00:40,209 --> 00:00:44,030 do so at TRXL.co/feedback. 12 00:00:44,379 --> 00:00:47,289 And again, that link is in the episodes show notes as well. 13 00:00:47,927 --> 00:00:48,797 On another note. 14 00:00:48,947 --> 00:00:53,117 It was absolutely amazing to see so many great people from the 15 00:00:53,117 --> 00:00:57,197 AEC tech universe and beyond at this year's Autodesk university. 16 00:00:57,677 --> 00:01:01,547 Look for a blog post with selfies with previous guests of the show, 17 00:01:01,937 --> 00:01:04,096 including the guest in today's episode. 18 00:01:04,516 --> 00:01:08,867 So in this episode, I welcome Marty Rozmanith, the co-founder and 19 00:01:08,867 --> 00:01:11,027 chief technology officer at Skema. 20 00:01:11,387 --> 00:01:14,747 Marty is an entrepreneur and building design and construction professional 21 00:01:14,777 --> 00:01:18,347 with a 30 plus year career in transforming the building industry. 22 00:01:18,917 --> 00:01:22,997 As co-founder and chief technology officer at Skema, Marty leads the team 23 00:01:22,997 --> 00:01:28,337 developing the Skema software suite, the world's first BIM knowledge reuse engine. 24 00:01:28,787 --> 00:01:32,387 Marty's career is a solid mix of technology startups, and global 25 00:01:32,387 --> 00:01:37,157 software behemoths that give him a unique perspective on the AEC industry. 26 00:01:37,607 --> 00:01:41,327 He spent five years in professional practice before specializing in 27 00:01:41,327 --> 00:01:46,037 AEC software, and he was recruited out of Autodesk to join the startup 28 00:01:46,067 --> 00:01:49,637 company called Charles River Software, which became ultimately 29 00:01:49,637 --> 00:01:51,107 Revit Technology Corporation. 30 00:01:51,527 --> 00:01:54,377 Marty is best known for his role leading the requirements 31 00:01:54,407 --> 00:01:56,057 team for the Revit product. 32 00:01:56,477 --> 00:02:01,067 When Autodesk acquired Revit in 2002, Marty spent several more years at 33 00:02:01,067 --> 00:02:02,747 Autodesk before going out on his own. 34 00:02:02,747 --> 00:02:06,857 Once again, to create companies that address modular and sustainable buildings. 35 00:02:07,307 --> 00:02:12,407 And before joining Skema, he spent 10 years at Dassault Systèmes as global sales 36 00:02:12,407 --> 00:02:15,257 director and strategy director for AEC. 37 00:02:15,737 --> 00:02:20,447 His work, applying modular approaches and digital twins in AEC has been published 38 00:02:20,447 --> 00:02:24,797 in the Wall Street Journal, Forbes magazine, and other professional journals. 39 00:02:25,307 --> 00:02:29,327 Marty not only holds a Bachelor of Architectural Engineering from Penn State, 40 00:02:29,357 --> 00:02:32,656 he also has an MBA from Boston University. 41 00:02:33,257 --> 00:02:36,857 In this episode, Marty takes us on his incredible journey through the world of 42 00:02:36,857 --> 00:02:42,177 AEC tech from self-taught programming skills to pioneering the use of 3d in 43 00:02:42,197 --> 00:02:48,047 AutoCAD in the early days, to Revit, then post-Autodesk at Dassault Systèmes and 44 00:02:48,047 --> 00:02:52,727 beyond, Marty shares unexpected twists and turns that shaped his career with 45 00:02:52,727 --> 00:02:56,597 the common thread of always trying to better connect design to construction. 46 00:02:57,158 --> 00:03:01,778 Listen in, as we explore the fascinating path that led Marty to where he is 47 00:03:01,778 --> 00:03:06,068 today and what challenges he's got his sights set on solving for our 48 00:03:06,068 --> 00:03:08,828 industry with his latest venture Skema. 49 00:03:09,248 --> 00:03:12,658 So without further ado, I bring you Marty Rozmanith. 50 00:03:18,931 --> 00:03:20,321 Marty, welcome to the podcast. 51 00:03:20,491 --> 00:03:21,161 Great to have you. 52 00:03:21,821 --> 00:03:22,241 Marty Rozmanith: Thanks. 53 00:03:22,411 --> 00:03:23,121 Great to be here. 54 00:03:23,839 --> 00:03:25,379 Evan Troxel: I'm really interested in your backstory. 55 00:03:25,679 --> 00:03:32,459 You, you've, you've been through so much in AEC tech, and I, I want you to tell 56 00:03:32,459 --> 00:03:36,939 that story of kind of where you've been, to, how you've gotten to where you are. 57 00:03:37,099 --> 00:03:40,219 I know that there's some, there, there's some stuff in there that, 58 00:03:40,219 --> 00:03:42,139 that it's just you, it's unexpected. 59 00:03:42,359 --> 00:03:45,699 And that, to me is, is gonna be kind of an interesting jumping 60 00:03:45,759 --> 00:03:47,139 off point for this conversation. 61 00:03:47,319 --> 00:03:51,418 So take it over and, and tell us kind of the path that you've been 62 00:03:51,418 --> 00:03:53,859 on over the last, I don't know how many decades you tell us. 63 00:03:55,190 --> 00:03:56,640 Marty Rozmanith: Yeah, about 30 years. 64 00:03:56,840 --> 00:03:58,240 A little more than 30 years now, actually. 65 00:03:58,420 --> 00:04:02,240 Um, geez, going all the way back. 66 00:04:02,440 --> 00:04:06,280 I mean, I started out in professional practice, like a, a lot of people 67 00:04:06,280 --> 00:04:07,440 that went into tech eventually. 68 00:04:07,660 --> 00:04:07,880 Um, 69 00:04:08,029 --> 00:04:08,149 Evan Troxel: Hmm. 70 00:04:08,755 --> 00:04:13,915 Marty Rozmanith: I went and, uh, was doing a lot of work, uh, with 71 00:04:14,155 --> 00:04:15,555 computers when I was in college. 72 00:04:16,055 --> 00:04:17,394 Um, I ended up. 73 00:04:18,010 --> 00:04:23,470 taking an AutoCAD class back in the very early days in the, in the eighties. 74 00:04:24,250 --> 00:04:31,800 And, um, you know, it was a drafting class and I was kind of not liking the fact 75 00:04:31,800 --> 00:04:38,400 that it couldn't do three D so I took lisp and I wrote an entire system so that 76 00:04:38,560 --> 00:04:40,640 two D AutoCAD could do three D models. 77 00:04:41,239 --> 00:04:41,459 Evan Troxel: Wow. 78 00:04:41,830 --> 00:04:44,080 Marty Rozmanith: When, when my professors saw that, they were like, 79 00:04:44,820 --> 00:04:50,280 you should just teach the AutoCAD lab . So, um, so that's kind of how I 80 00:04:50,280 --> 00:04:52,640 got into to tech, uh, in this world. 81 00:04:52,940 --> 00:04:55,880 And, uh, but of course I was just, you know, a college student who didn't really 82 00:04:55,880 --> 00:04:57,480 know anything about professional practice. 83 00:04:57,540 --> 00:04:59,200 And so after I got outta school, 84 00:05:00,340 --> 00:05:02,740 I, I, graduated into a recession, which is not uncommon. 85 00:05:03,040 --> 00:05:05,420 Uh, I know so many people who graduated into recessions and 86 00:05:05,420 --> 00:05:06,500 had to do creative things. 87 00:05:06,500 --> 00:05:10,060 So I ended up moving to California where I went for, to work for a 88 00:05:10,060 --> 00:05:14,540 very small architecture firm, um, where I had told 'em all about, you 89 00:05:14,540 --> 00:05:16,900 know, my CAD proficiency, but a lot of what they did was hand drafting. 90 00:05:16,900 --> 00:05:19,700 So I got to draft on Vellum and, you know, do all those things 91 00:05:19,700 --> 00:05:22,820 that old school guys did, uh, when you first started out in design. 92 00:05:24,040 --> 00:05:27,180 Uh, and then the recession caught up with the West Coast, and I got 93 00:05:27,180 --> 00:05:29,420 laid off like nine months after I moved all the way across the country. 94 00:05:29,640 --> 00:05:37,020 So, uh, . So, so I ended up deciding, uh, that I would try to tap some contacts 95 00:05:37,170 --> 00:05:40,820 from Penn State where I had graduated, and a lot of them were in the Bay 96 00:05:40,820 --> 00:05:43,860 Area, so I just started reaching out to people and I landed a job up in San 97 00:05:43,860 --> 00:05:48,220 Francisco, which was, happened to be a, a happy accident since that's, you 98 00:05:48,220 --> 00:05:52,180 know, where the nucleus of tech was in, uh, the late eighties, early nineties. 99 00:05:52,520 --> 00:05:55,980 Um, and so I started working for an architecture firm up there. 100 00:05:57,415 --> 00:06:00,515 And, uh, and did work on architecture practice and also 101 00:06:00,515 --> 00:06:01,475 instructional engineering. 102 00:06:02,375 --> 00:06:07,075 And it got to the point where, um, I had worked for a couple firms. 103 00:06:07,695 --> 00:06:11,595 I'd been in professional practice about five years, uh, got to 104 00:06:11,595 --> 00:06:12,915 know people in the Bay Area. 105 00:06:13,475 --> 00:06:16,555 I ended up being one of the co-chairs of the computer forum for 106 00:06:16,755 --> 00:06:18,635 the A I a San Francisco chapter. 107 00:06:19,255 --> 00:06:21,875 We would have a, a graphics exhibit every year. 108 00:06:22,735 --> 00:06:28,395 Um, so I think I'm the first person to hold a VR competition back in 1994 109 00:06:28,655 --> 00:06:33,875 at the San Francisco a i a, uh, which is pretty fun because I remember SOM 110 00:06:34,075 --> 00:06:39,675 Wheeling in a refrigerator size, Silicon Graphics, indigo computer because 111 00:06:39,675 --> 00:06:42,955 they had a three D model of the Dubai airport they were designing at the time. 112 00:06:42,975 --> 00:06:46,034 And you could walk around it at like one frame per second. 113 00:06:46,419 --> 00:06:46,709 Evan Troxel: Yeah. 114 00:06:46,939 --> 00:06:47,229 Yeah. 115 00:06:47,375 --> 00:06:47,595 Marty Rozmanith: So, 116 00:06:48,169 --> 00:06:48,389 Evan Troxel: Wow. 117 00:06:48,775 --> 00:06:50,515 Marty Rozmanith: but it was pretty interesting, you know, just to see the, 118 00:06:50,815 --> 00:06:51,875 you know, where things were headed. 119 00:06:52,495 --> 00:06:52,715 Um. 120 00:06:55,430 --> 00:06:57,790 I gotta the point where I had to make a decision about whether I was 121 00:06:57,790 --> 00:07:01,750 gonna commit to tech or con con, continue being committed to being 122 00:07:01,790 --> 00:07:03,150 a designer and designing buildings. 123 00:07:03,150 --> 00:07:05,950 And I thought, well, if I commit to tech, I'll probably make a bigger 124 00:07:05,970 --> 00:07:09,430 impact than I would, you know, working on designing buildings. 125 00:07:09,650 --> 00:07:13,790 Um, and so I did and I started my own consulting company and I actually had 126 00:07:13,790 --> 00:07:15,310 a lot of clients in San Francisco. 127 00:07:15,490 --> 00:07:17,110 You know, HOK was a client. 128 00:07:17,170 --> 00:07:20,910 Uh, the Federal Reserve Blank Bank was a client, like a lot of people that needed, 129 00:07:21,650 --> 00:07:26,390 uh, tech infrastructure for anything to do with facilities, whether it was designing 130 00:07:26,390 --> 00:07:27,590 facilities or operating facilities. 131 00:07:27,610 --> 00:07:28,390 We ended up doing that. 132 00:07:29,730 --> 00:07:29,950 Um. 133 00:07:31,520 --> 00:07:34,960 I got to know from the AIAI got to know the Autodesk marketing people 'cause they 134 00:07:35,440 --> 00:07:37,000 actually sponsored the graphics exhibit. 135 00:07:37,060 --> 00:07:40,360 And AutoCAD was one of the prizes that, that was the grand prize for 136 00:07:40,360 --> 00:07:42,280 those who, who won the exhibit. 137 00:07:42,659 --> 00:07:47,480 Um, and through that relationship I actually got recruited into Autodesk, um, 138 00:07:47,670 --> 00:07:51,040 with the proviso that I would actually move across the country to New England 139 00:07:51,040 --> 00:07:52,440 because that's where the job was located. 140 00:07:52,680 --> 00:07:54,560 'cause they had just bought a company called Soft Desks. 141 00:07:55,420 --> 00:07:58,840 Um, and I had just gotten done implementing soft desks at the firm 142 00:07:58,920 --> 00:08:01,880 I worked at, which was RMW, uh, which is still around today, kicking 143 00:08:01,910 --> 00:08:03,960 hard, uh, 30 something years later. 144 00:08:04,500 --> 00:08:11,710 And so, um, Autodesk moved me to, to, to New England and I started working on 145 00:08:11,710 --> 00:08:15,110 the first, uh, software product I ever did, which was Architectural Desktop, 146 00:08:15,810 --> 00:08:17,670 uh, which was an AutoCAD based product. 147 00:08:18,010 --> 00:08:21,390 And I actually got to the Revit startup because I was out there Marketing 148 00:08:21,390 --> 00:08:23,950 Architectural Desktop, which that was the number one product at the time. 149 00:08:23,950 --> 00:08:25,230 And I was at all the trade shows. 150 00:08:25,250 --> 00:08:29,990 So I think the, the venture capitalists that were backing Revit. 151 00:08:30,730 --> 00:08:35,030 Got my business card at one of the events, whether it was, I think it was AEC systems 152 00:08:35,130 --> 00:08:37,510 at the time, and handed it to founders. 153 00:08:37,690 --> 00:08:41,590 And one day I got a call, uh, from this guy with this Russian accent 154 00:08:41,610 --> 00:08:43,710 who said, you should come down here and see what we're doing. 155 00:08:44,770 --> 00:08:49,910 Uh, so it was all very mysterious, you know, and I drove down to Boston and, 156 00:08:50,389 --> 00:08:51,249 Evan Troxel: No hesitation. 157 00:08:51,800 --> 00:08:54,530 Marty Rozmanith: well, no, I, I, well, yeah, it took a few phone 158 00:08:54,530 --> 00:08:57,450 calls for me to go, okay, lemme go and see what these guys are up 159 00:08:57,450 --> 00:08:57,570 to, 160 00:08:57,749 --> 00:08:58,049 Evan Troxel: All right. 161 00:08:58,530 --> 00:09:00,290 Marty Rozmanith: they were hinting at what they, what they had. 162 00:09:00,310 --> 00:09:02,090 And, you know, we were trying to do some things in 163 00:09:02,090 --> 00:09:03,210 architectural desktop at the time. 164 00:09:03,270 --> 00:09:07,850 And, um, I went down and, and these guys kind of took a chance. 165 00:09:07,850 --> 00:09:11,090 They knew I worked for Autodesk, and so revealing what they were doing was 166 00:09:11,090 --> 00:09:12,490 sort of a risky proposition for them. 167 00:09:12,550 --> 00:09:14,490 And, but they decided to show me anyway. 168 00:09:14,510 --> 00:09:18,130 And, and I, what I saw was, you know, the nucleus of something 169 00:09:18,130 --> 00:09:19,330 that was pretty amazing. 170 00:09:20,070 --> 00:09:22,330 It, it was very, very, very early. 171 00:09:22,420 --> 00:09:22,770 Right? 172 00:09:23,004 --> 00:09:23,294 Evan Troxel: Yeah. 173 00:09:23,484 --> 00:09:23,774 Yeah. 174 00:09:24,070 --> 00:09:24,290 Marty Rozmanith: um. 175 00:09:25,495 --> 00:09:28,955 But based on that, um, I decided to join that team. 176 00:09:29,895 --> 00:09:32,995 Um, and there were only a couple dozen of us at the time and we were 177 00:09:32,995 --> 00:09:36,355 in this building in Framingham that everybody, uh, calls the Pink Palace. 178 00:09:36,695 --> 00:09:43,205 So if you know Framingham Mass, you know, this building, um, in incidentally for 179 00:09:43,205 --> 00:09:48,525 Full Circle is now where the work bar space that we actually use for Skema is. 180 00:09:48,525 --> 00:09:52,725 So actually one of our employees, still goes to that building that he used to go 181 00:09:52,725 --> 00:09:54,525 to when he was at Charles River Software. 182 00:09:54,525 --> 00:09:58,485 And so, yeah, so Charles River software software was based in Framingham 183 00:09:58,905 --> 00:10:05,565 and we had, you know, developers, uh, with PCs connected with hard 184 00:10:05,665 --> 00:10:07,445 cables 'cause wifi didn't exist yet. 185 00:10:07,445 --> 00:10:12,445 Writing this piece of software, um, in c plus plus and eventually, um. 186 00:10:13,860 --> 00:10:18,080 We started going to market and uh, and part of what I did was, was sign up. 187 00:10:18,080 --> 00:10:19,880 The first dozen customers, 188 00:10:20,340 --> 00:10:22,280 uh, you know, that I thought of as pioneers. 189 00:10:22,280 --> 00:10:26,600 They, they were really people that I knew from having been not only a consultant, 190 00:10:26,780 --> 00:10:34,840 but also, um, some of the more, um, vocal people, uh, from my Autodesk days. 191 00:10:35,140 --> 00:10:38,480 So, you know, I wanted to show them what we were working on and some of 192 00:10:38,480 --> 00:10:39,840 them really gravitated towards it. 193 00:10:39,870 --> 00:10:41,160 Some of them didn't get it. 194 00:10:41,860 --> 00:10:45,600 Uh, but those that gravitated towards it formed a nucleus of pretty important, 195 00:10:46,060 --> 00:10:51,120 um, friends of the family that helps steer us so that we got the product 196 00:10:51,360 --> 00:10:56,600 market fit in a way that actually worked for architects as opposed to just, um. 197 00:10:57,960 --> 00:10:59,500 You know, trying to come up with something you can sell. 198 00:10:59,585 --> 00:11:01,725 Uh, so we were trying to, you know, we were always focused on what 199 00:11:01,725 --> 00:11:02,725 problem is it we're trying to solve. 200 00:11:03,065 --> 00:11:06,045 And, uh, the problem that we chose to solve was coordinating construction 201 00:11:06,045 --> 00:11:07,485 drawings and using a model to do that. 202 00:11:07,505 --> 00:11:11,405 And so I was thinking of Revit as this rubberized cardboard building 203 00:11:11,405 --> 00:11:14,525 that you build so that it'll do your construction drawings so you don't have 204 00:11:14,525 --> 00:11:17,805 to constantly deal with 300 AutoCAD files, which is what used to have 205 00:11:17,805 --> 00:11:19,405 to do before, before the Revit days. 206 00:11:19,729 --> 00:11:20,079 Evan Troxel: Right. 207 00:11:20,585 --> 00:11:24,605 Marty Rozmanith: Um, you know, there's a lot of, uh, we put a lot of things 208 00:11:24,605 --> 00:11:28,165 into it because it was a model-based thing, and it's driven by a database 209 00:11:29,235 --> 00:11:33,485 that said, from the time we wrote it, you know, that database is a big fat file 210 00:11:33,485 --> 00:11:36,085 that sits in a Microsoft file system. 211 00:11:36,305 --> 00:11:39,045 So it's not something that's served in a client server database. 212 00:11:39,145 --> 00:11:44,125 And, uh, you know, it's, it's obviously an old piece of software at this point, even 213 00:11:44,125 --> 00:11:47,325 though it's still kicking hard, producing lots of deliverables for people that 214 00:11:47,325 --> 00:11:48,645 they're getting paid on projects with. 215 00:11:49,119 --> 00:11:49,469 Evan Troxel: right. 216 00:11:49,585 --> 00:11:50,165 Marty Rozmanith: But, um. 217 00:11:52,045 --> 00:11:57,345 You know, after, uh, so we, we, we had some, we had a very, uh, aggressive 218 00:11:57,345 --> 00:12:03,715 marketing vp, um, who was the guy who had the market Lotus notes against Microsoft. 219 00:12:03,815 --> 00:12:04,235 So he 220 00:12:04,239 --> 00:12:04,899 Evan Troxel: Oh yeah. 221 00:12:05,075 --> 00:12:06,995 Marty Rozmanith: he knew all the gorilla tactics and he pulled 'em 222 00:12:06,995 --> 00:12:09,275 all out of his bag all the time. 223 00:12:09,935 --> 00:12:13,315 Um, it was a lot of fun learning guerrilla marketing tactics from this guy. 224 00:12:13,495 --> 00:12:15,675 Uh, 'cause he wouldn't, he wouldn't pull any punches. 225 00:12:16,815 --> 00:12:23,595 Uh, and we obviously got, um, I think we were on the, the, the radar for most 226 00:12:23,595 --> 00:12:25,755 of the big CAG companies, especially since we would go to all the major 227 00:12:25,755 --> 00:12:26,795 trade shows and they would see us. 228 00:12:26,975 --> 00:12:30,795 Um, we weren't shy that we, we spent VC money and got huge boosts 229 00:12:30,795 --> 00:12:31,715 right next to the big players. 230 00:12:31,815 --> 00:12:33,715 And that's how you did it back in those days. 231 00:12:33,745 --> 00:12:35,115 That today it's a little bit different. 232 00:12:35,275 --> 00:12:39,795 Although we are rebooting a few of the Revit playbook, um, steps like 233 00:12:39,815 --> 00:12:44,795 the, the Pioneer customers that formed the nucleus of your product feedback. 234 00:12:44,795 --> 00:12:47,475 And then eventually what, what we did at Revit, which we're doing now, is 235 00:12:47,475 --> 00:12:50,275 that that first dozen or so pioneer. 236 00:12:51,900 --> 00:12:58,760 You know, users that you have those firms, they're like magnets that attract the 237 00:12:58,760 --> 00:13:00,200 next 10 in their region of the country. 238 00:13:00,460 --> 00:13:04,400 So we eventually got to the point where we had a hundred, 120 firms 239 00:13:04,550 --> 00:13:06,680 that were our customer advisory board. 240 00:13:06,680 --> 00:13:13,540 And we would go around the country meet with all those firms on a probably twice 241 00:13:13,580 --> 00:13:16,580 a year basis just to go through roadmap and what we were thinking of doing. 242 00:13:16,640 --> 00:13:19,380 And we would basically make them argue with each other over 243 00:13:19,380 --> 00:13:20,460 what was more important to them. 244 00:13:21,160 --> 00:13:24,340 And that worked actually pretty well, um, because we would hear not 245 00:13:24,340 --> 00:13:26,940 just what was important, but people advocating for certain things and 246 00:13:26,940 --> 00:13:28,500 other people bouncing ideas off. 247 00:13:28,500 --> 00:13:31,340 And you know, we, we always said, if you ask 10 architects, 248 00:13:31,340 --> 00:13:32,580 you'll get 15 different opinions. 249 00:13:33,480 --> 00:13:36,300 Uh, because, you know, designers love to consider all sides. 250 00:13:36,720 --> 00:13:40,580 And so we, we got to work that working for us by just having people debate. 251 00:13:41,320 --> 00:13:46,130 What are the most important things for Revit to be able to do for the, the, the 252 00:13:46,130 --> 00:13:50,210 user base out there, you know, and what is the 10% that we shouldn't put in there 253 00:13:50,210 --> 00:13:51,890 that's special to somebody's practice? 254 00:13:51,890 --> 00:13:56,130 And they'll do that by doing something to the family editor or some script 255 00:13:56,130 --> 00:13:57,090 eventually that they'll write. 256 00:13:57,390 --> 00:14:01,210 Um, we're, we're doing some of that with Skema now. 257 00:14:01,310 --> 00:14:08,150 But, um, yeah, I, after Autodesk acquired the company, I spent three years there. 258 00:14:08,910 --> 00:14:11,830 I wrote some things which I thought would be useful for Autodesk to implement. 259 00:14:12,110 --> 00:14:13,710 A lot of that stuff never got implemented. 260 00:14:14,210 --> 00:14:16,830 Um, part partly because I was more of a product guy. 261 00:14:16,830 --> 00:14:18,230 I wasn't really a business and sales guy. 262 00:14:18,890 --> 00:14:21,950 So after I, after I left Autodesk, three years after the 263 00:14:21,950 --> 00:14:23,390 acquisition, I went and got an MBA. 264 00:14:23,710 --> 00:14:25,750 'cause I knew at some point in the future if I ever did this again, I 265 00:14:25,750 --> 00:14:28,110 would've to argue with those business and sales guys about, you know, 266 00:14:29,170 --> 00:14:32,470 Not just what's a good idea, but what actually makes sense for the business. 267 00:14:32,739 --> 00:14:33,519 Evan Troxel: You had to speak their 268 00:14:33,799 --> 00:14:34,239 language, right? 269 00:14:34,455 --> 00:14:34,745 Marty Rozmanith: Yeah. 270 00:14:34,745 --> 00:14:38,265 So I went, uh, like immediately thereafter and got an MBA and started 271 00:14:38,265 --> 00:14:39,825 working on my own startup companies. 272 00:14:39,825 --> 00:14:42,545 The first ones being all about the building industry, 273 00:14:42,605 --> 00:14:44,625 but not about design intent. 274 00:14:45,565 --> 00:14:47,065 Uh, more about means and methods. 275 00:14:47,685 --> 00:14:52,305 Um, so, um, there was one that was manufacturing, CNC steel 276 00:14:52,365 --> 00:14:57,265 frames off Revit models to try and accelerate the precision and delivery 277 00:14:58,265 --> 00:14:59,585 specifically in multifamily housing. 278 00:14:59,845 --> 00:15:04,905 Uh, there was another one that we did that was, uh, after Katrina hit, um. 279 00:15:06,025 --> 00:15:11,245 Uh, how, uh, very fast assembly housing for the Gulf Coast that was made out. 280 00:15:11,305 --> 00:15:13,845 It looked like a low country Mississippi cottage, but it was 281 00:15:13,845 --> 00:15:17,605 made out of lightweight, precast concrete, and we physically tested 282 00:15:17,705 --> 00:15:19,765 it to 160 mile an hour winds. 283 00:15:20,385 --> 00:15:24,205 Uh, so there's a prototype still sitting there somewhere, uh, in, in 284 00:15:24,375 --> 00:15:26,045 Pascagoula, Mississippi actually. 285 00:15:26,185 --> 00:15:30,645 And, uh, you know, it's, it's been hit by like 25 hurricanes and it still looks 286 00:15:30,739 --> 00:15:31,319 Evan Troxel: At this point, 287 00:15:32,355 --> 00:15:32,845 Marty Rozmanith: amazing. 288 00:15:33,115 --> 00:15:35,525 It's the actual most amazing building I've probably ever put out. 289 00:15:35,545 --> 00:15:37,685 But, um, not, not many people know about it. 290 00:15:38,545 --> 00:15:40,405 Uh, and a lot of, so a lot of startups like that. 291 00:15:40,405 --> 00:15:41,965 Some of them worked, some of them didn't work. 292 00:15:42,145 --> 00:15:43,885 Um, not all of them were in ac. 293 00:15:44,285 --> 00:15:47,805 I did a couple SaaS products that were just general consumer SaaS products, 294 00:15:47,905 --> 00:15:51,165 um, in web publishing and some other stuff where I got to learn about, 295 00:15:51,225 --> 00:15:53,085 you know, running a company, , making 296 00:15:53,204 --> 00:15:54,104 Evan Troxel: Mm mm-Hmm. 297 00:15:54,305 --> 00:15:56,645 Marty Rozmanith: um, general marketing and sales, that sort of stuff. 298 00:15:57,365 --> 00:16:01,505 And then, uh, finally got to the point where I just decided I wanted to go 299 00:16:01,505 --> 00:16:04,705 back into ac, um, partly because. 300 00:16:06,265 --> 00:16:10,265 I knew that Revit would need several years just to kinda get on its feet. 301 00:16:11,205 --> 00:16:12,785 Um, and then. 302 00:16:14,580 --> 00:16:16,940 I just took a look around the industry and thought, okay, what, 303 00:16:16,940 --> 00:16:21,980 what's, where could I make impact now that several years have passed? 304 00:16:22,120 --> 00:16:25,420 And so I started looking at the various players and I thought actually DA 305 00:16:25,420 --> 00:16:27,140 Systems had some pretty good technology, 306 00:16:27,920 --> 00:16:29,180 um, that they had developed. 307 00:16:29,360 --> 00:16:32,140 Uh, obviously the big product, everybody knows there is Katia 308 00:16:32,240 --> 00:16:33,500 and the other ones SolidWorks. 309 00:16:33,500 --> 00:16:36,340 So those are all modeling products, but they actually have, you know, 310 00:16:36,340 --> 00:16:40,060 quite a large tech stack that's used in aerospace and automotive industries. 311 00:16:40,060 --> 00:16:44,020 And given the fact that I had been in some manufacturing startups, I thought, all 312 00:16:44,020 --> 00:16:46,940 right, well if I have to figure out, you know, how to apply some technology and 313 00:16:46,940 --> 00:16:50,860 some work practices from manufacturing to construction to, so systems is 314 00:16:51,020 --> 00:16:51,780 probably a pretty good place to do it. 315 00:16:52,060 --> 00:16:56,100 So I went, uh, and spent 10 years at the so systems. 316 00:16:56,725 --> 00:17:01,290 Kinda advocating DFMA and productizing and industrializing construction 317 00:17:01,290 --> 00:17:02,210 to make it more efficient. 318 00:17:02,990 --> 00:17:06,490 And that whole thing about trying to connect design to construction 319 00:17:06,510 --> 00:17:08,290 is something I've been doing ever since I was in college. 320 00:17:08,410 --> 00:17:14,130 I wrote a, I wrote a, my thesis paper at Penn State back in 89 on a system 321 00:17:14,130 --> 00:17:15,810 to connect design and construction. 322 00:17:15,960 --> 00:17:18,690 It's, I, I came across it in my basement the other day, 323 00:17:19,608 --> 00:17:19,829 Evan Troxel: Wow. 324 00:17:19,829 --> 00:17:20,229 That's 325 00:17:20,230 --> 00:17:24,250 Marty Rozmanith: Um, and so, you know, there, there are some of it, my colleagues 326 00:17:24,250 --> 00:17:27,650 who refer to this as a disease, like, you know, we've just been at this for so many 327 00:17:27,650 --> 00:17:29,130 decades, we can't leave it alone now. 328 00:17:29,230 --> 00:17:30,570 And that's kind of how I am about it. 329 00:17:31,749 --> 00:17:31,969 Evan Troxel: Wow. 330 00:17:32,219 --> 00:17:33,529 There, there's so much there. 331 00:17:33,689 --> 00:17:35,969 I I, I kind of want to go back to the beginning for a moment 332 00:17:35,969 --> 00:17:41,409 because you wrote your own three d modeling lisp routines for AutoCAD. 333 00:17:41,459 --> 00:17:42,569 Where did that come from? 334 00:17:42,569 --> 00:17:47,489 Like what, because they don't teach c plus plus or lisp in architecture school. 335 00:17:47,489 --> 00:17:47,769 Right. 336 00:17:47,789 --> 00:17:51,929 And so obviously you're self starting, and so I'm just wondering like, what, 337 00:17:52,229 --> 00:17:57,329 why did, why did you decide to do that in the very beginning and, and how did you 338 00:17:57,329 --> 00:17:58,729 decide, how did you accomplish that? 339 00:17:59,455 --> 00:18:02,635 Marty Rozmanith: Um, so I wasn't in an architecture program. 340 00:18:02,835 --> 00:18:05,555 I was in an architectural engineering program at, at Penn State. 341 00:18:05,975 --> 00:18:08,635 And, uh, so you're pretty technical when you're in that program. 342 00:18:09,535 --> 00:18:13,995 Uh, the, you know, computers in that program, these are, you know, this 343 00:18:13,995 --> 00:18:17,515 is eighties, so I think EABs existed. 344 00:18:17,735 --> 00:18:23,155 So you used it for structural simulation, but there was really, other than general 345 00:18:23,275 --> 00:18:26,475 drafting software that people used for mechanical cad, there wasn't anything 346 00:18:26,795 --> 00:18:28,875 specifically dedicated to AEC at the time. 347 00:18:29,615 --> 00:18:30,915 And so I. 348 00:18:31,130 --> 00:18:36,550 Um, I was actually trying to rationalize a project that was a, 349 00:18:36,790 --> 00:18:40,710 a multi-family residential project, um, that someday I knew was working 350 00:18:40,730 --> 00:18:44,710 on, and it, and it was, it was all to do with roof slopes and stuff. 351 00:18:44,730 --> 00:18:46,870 And so I just said, how can I make this do it? 352 00:18:47,559 --> 00:18:47,779 Evan Troxel: Mm 353 00:18:49,030 --> 00:18:52,910 Marty Rozmanith: I wrote my first computer program in middle school. 354 00:18:53,330 --> 00:18:58,870 Uh, I wrote a game for the Apple two e , which was, it was a moon game. 355 00:18:59,170 --> 00:19:04,070 Uh, most of the game was in basic, but in order on a machine of that era to 356 00:19:04,070 --> 00:19:07,510 get the graphics to be fast enough, you had to write them in assembler, 357 00:19:07,510 --> 00:19:09,390 which is basically raw machine code. 358 00:19:09,490 --> 00:19:10,630 So, you know. 359 00:19:11,685 --> 00:19:14,345 In middle school, I learned how to write assembler code. 360 00:19:14,685 --> 00:19:20,385 Um, and so I wrote this game and eventually, um, in sort of computer 361 00:19:20,455 --> 00:19:23,545 circles, I got a, you know, you would pass things around on floppy 362 00:19:23,545 --> 00:19:25,985 disc and I got this floppy disc because I had this moon game on. 363 00:19:25,985 --> 00:19:27,065 I'm like, I wrote this game. 364 00:19:28,704 --> 00:19:29,284 Evan Troxel: That's awesome. 365 00:19:29,325 --> 00:19:34,025 Marty Rozmanith: So, so, you know, I, I had written programs ever since I was 366 00:19:34,025 --> 00:19:39,665 in middle school, and so I just, you know, it was mainly self-taught, um, 367 00:19:39,815 --> 00:19:43,305 just learning how to do programming, uh, 368 00:19:43,455 --> 00:19:43,745 with 369 00:19:43,934 --> 00:19:44,574 Evan Troxel: that outta books? 370 00:19:44,634 --> 00:19:45,854 Was that outta magazines? 371 00:19:45,854 --> 00:19:46,254 Because I 372 00:19:46,340 --> 00:19:49,520 Marty Rozmanith: It was at a, mostly, mostly books and trial and error. 373 00:19:49,900 --> 00:19:53,440 Um, I, I wrote those programs on an Apple two E. 374 00:19:53,460 --> 00:19:56,160 The, the school that I was at had Apple two E. 375 00:19:57,020 --> 00:20:01,960 Um, I eventually got like an Atari 400 that I wrote basic programs on at home. 376 00:20:02,280 --> 00:20:04,520 'cause it was a little bit better than having a game console. 377 00:20:05,140 --> 00:20:06,840 So somehow I talked my parents into it. 378 00:20:07,034 --> 00:20:07,324 Evan Troxel: Nice. 379 00:20:07,620 --> 00:20:10,680 Marty Rozmanith: Um, but you know, I just had a general awareness of 380 00:20:10,790 --> 00:20:14,520 what it takes to write something like that and the structure of it. 381 00:20:14,740 --> 00:20:18,040 And I realized that this lisp language was something that you 382 00:20:18,040 --> 00:20:20,800 could extend functionality with an AutoCAD so that I just did it. 383 00:20:21,620 --> 00:20:25,840 Um, I don't know you, I just didn't think too hard about it. 384 00:20:25,840 --> 00:20:29,080 I just started working on it and figured out how to structure it and it worked. 385 00:20:29,860 --> 00:20:33,440 Um, probably nobody else would ever be able to figure out how to use it, but 386 00:20:33,540 --> 00:20:33,840 you know, 387 00:20:33,869 --> 00:20:34,219 Evan Troxel: Right. 388 00:20:36,369 --> 00:20:38,779 Well, and back in those days, AutoCAD was running on Doss. 389 00:20:38,779 --> 00:20:39,019 Right. 390 00:20:39,079 --> 00:20:43,339 And, and just, just to kind of reiterate the things that you're saying, the the 391 00:20:43,339 --> 00:20:47,059 first thing that I, my first computer was also an Apple two e and I would 392 00:20:47,059 --> 00:20:50,059 program things in basic, and you're, you're much more of the engineer side 393 00:20:50,059 --> 00:20:53,259 of architecture and I'm much more of the designer side of architecture because 394 00:20:53,509 --> 00:20:58,619 going through that process, uh, my first personal computer was a Commodore 64 395 00:20:58,619 --> 00:21:00,539 that I bought at Toys Russ of all places. 396 00:21:00,909 --> 00:21:01,259 Right. 397 00:21:01,399 --> 00:21:06,299 And I wrote, like, you a game, but I copied it out of a magazine. 398 00:21:06,299 --> 00:21:07,379 And that's what we had to do back then. 399 00:21:07,379 --> 00:21:07,539 Right? 400 00:21:07,539 --> 00:21:12,059 We had to, I had to read the text in the magazine and then, or a book and try to 401 00:21:12,189 --> 00:21:14,299 write that same code and, and then go 402 00:21:14,299 --> 00:21:16,179 back and find where I, where I made a mistake 403 00:21:16,679 --> 00:21:17,299 to fix it. 404 00:21:17,959 --> 00:21:21,299 And I realized right then that I was not gonna do that anymore like that. 405 00:21:21,899 --> 00:21:25,659 I, I, and because even then on the Commodore, it was like, how do I, I. 406 00:21:27,044 --> 00:21:29,404 I can save this to a floppy, but at some point like that, 407 00:21:29,434 --> 00:21:30,924 that that program was just lost. 408 00:21:30,924 --> 00:21:31,204 Right. 409 00:21:31,204 --> 00:21:31,964 It was just gone. 410 00:21:32,264 --> 00:21:36,564 And, and to, for you to stick with it and then to take it to those 411 00:21:36,564 --> 00:21:39,404 other levels, I think is, it just shows how like we're, we're coming 412 00:21:39,584 --> 00:21:43,164 at this, this problem of architecture and, and AEC from different places. 413 00:21:43,304 --> 00:21:48,724 But I, I find it so fascinating that so much of the innovation that we see today 414 00:21:49,184 --> 00:21:54,004 is based off somebody scratching their own itch and the intrinsic motivation 415 00:21:54,344 --> 00:21:59,884 of, of people to teach themselves a thing to do, to make something happen. 416 00:22:00,024 --> 00:22:02,564 And that just set the whole trajectory for your entire career. 417 00:22:02,954 --> 00:22:06,284 It's just kind of incredible to look back at it and think about it that way. 418 00:22:06,430 --> 00:22:07,240 Marty Rozmanith: Yeah, it's pretty cool. 419 00:22:10,175 --> 00:22:13,265 . It's also just being given the opportunity to do some practical applications 420 00:22:13,485 --> 00:22:14,785 so that you have some confidence. 421 00:22:14,785 --> 00:22:20,265 Like, um, my mother at the time was a dentist and she had this crazy thing 422 00:22:20,265 --> 00:22:25,105 where she had these file drawers full of like index cards where the, her 423 00:22:25,105 --> 00:22:28,665 staff had to figure out, all right, six from months from now, we have 424 00:22:28,865 --> 00:22:32,025 to send this person a reminder to come in and get their teeth cleaned, 425 00:22:32,025 --> 00:22:32,305 right? 426 00:22:32,805 --> 00:22:35,425 And I'm like, that's such an easy problem to solve for a computer. 427 00:22:35,525 --> 00:22:38,225 You know, you don't need an army of people sorting through index cards 428 00:22:38,225 --> 00:22:40,345 every week trying to figure out who the hell they should mail things 429 00:22:40,419 --> 00:22:40,839 Evan Troxel: mm-Hmm. 430 00:22:41,165 --> 00:22:43,185 Marty Rozmanith: So I actually took the guitar 400 and I wrote 431 00:22:43,185 --> 00:22:45,465 her a database program that would manage the entire, like. 432 00:22:46,445 --> 00:22:51,695 Process of, um, the re the re you know, essentially scheduling people 433 00:22:51,755 --> 00:22:55,415 six months out to, to do this and then basically printing all the labels 434 00:22:55,415 --> 00:22:58,175 that they could just use to stick on a postcard to send it to the person. 435 00:22:59,075 --> 00:23:02,015 Um, and so, you know, when you get the opportunity to do some practical 436 00:23:02,015 --> 00:23:07,295 application of just some strange weird skill that you have as a computer nerd, 437 00:23:07,835 --> 00:23:11,375 um, and you actually see that, you know, all of a sudden, like these 10 people 438 00:23:11,735 --> 00:23:12,935 actually, it made their job easier. 439 00:23:13,529 --> 00:23:13,819 Evan Troxel: Yeah. 440 00:23:13,995 --> 00:23:15,655 Marty Rozmanith: Um, it's, it's very encouraging. 441 00:23:15,995 --> 00:23:19,865 Um, you know, that said, I didn't really know what I was 442 00:23:19,865 --> 00:23:20,745 gonna do when I went to college. 443 00:23:21,025 --> 00:23:23,225 I thought I might do con computer science. 444 00:23:23,765 --> 00:23:27,185 Um, and I, I really only applied to Penn State and the University 445 00:23:27,185 --> 00:23:28,905 of Texas at, at, at Austin, 446 00:23:29,659 --> 00:23:29,779 Evan Troxel: Hmm. 447 00:23:30,245 --> 00:23:32,225 Marty Rozmanith: and UT lost my application. 448 00:23:32,305 --> 00:23:34,505 I was like, well, they don't have a good database if. 449 00:23:36,569 --> 00:23:37,709 Evan Troxel: You disqualified them. 450 00:23:37,939 --> 00:23:38,229 They 451 00:23:38,320 --> 00:23:40,560 Marty Rozmanith: they disqualify themselves and then, then they accept me. 452 00:23:40,560 --> 00:23:42,720 So I was like, alright, well this is an easy decision, I'll just go there. 453 00:23:42,780 --> 00:23:49,440 But, um, like, uh, I, I had to figure out a way to, to, to get, um, on 454 00:23:49,440 --> 00:23:53,480 the main campus and so I actually applied as a ceramic science and 455 00:23:53,720 --> 00:23:57,280 engineering major and eventually switched into architectural engineering. 456 00:23:57,844 --> 00:23:58,064 Evan Troxel: Hmm. 457 00:23:58,240 --> 00:24:00,280 Marty Rozmanith: but you know, sometimes things happen for a reason and you 458 00:24:00,280 --> 00:24:02,840 just end up where you're supposed to be and that's kind of how it worked out. 459 00:24:03,304 --> 00:24:03,594 Evan Troxel: Yeah. 460 00:24:03,724 --> 00:24:04,554 Super interesting. 461 00:24:04,794 --> 00:24:07,754 I what you, you talked about that the 10 people who found value 462 00:24:07,774 --> 00:24:08,954 and the thing that you did and, 463 00:24:09,014 --> 00:24:12,034 and that still drives people today in AEC who are writing 464 00:24:12,034 --> 00:24:12,954 grasshopper scripts, right. 465 00:24:12,954 --> 00:24:17,114 For their own studio or, and it, and it's, it's dynamo and grasshopper and, 466 00:24:17,114 --> 00:24:21,994 you know, the visual coding, no code kind of tools that people now have access to. 467 00:24:22,224 --> 00:24:26,594 Very different obviously than, than what we had growing up from a programming 468 00:24:26,594 --> 00:24:33,074 standpoint, but that people still enjoy doing, experiencing that exact scenario. 469 00:24:33,214 --> 00:24:38,034 And, and that's still what drives a lot of innovation in AEC, it's, it's 470 00:24:38,234 --> 00:24:40,994 actually pretty incredible that that threat is still alive very well. 471 00:24:42,245 --> 00:24:44,175 Marty Rozmanith: Yeah, one of the, and so, um, 472 00:24:48,035 --> 00:24:53,195 I kind of stopped directly writing code myself because I realized having done 473 00:24:53,195 --> 00:24:56,675 it a few times, that there were people way better than me at writing that code. 474 00:24:56,675 --> 00:25:01,475 And once things got complex enough to be c and c plus plus, I was like, I'm 475 00:25:01,475 --> 00:25:02,995 not the best guy to write that code. 476 00:25:03,255 --> 00:25:06,235 Uh, 'cause that's like, you have that, you have to gone to school for that and, 477 00:25:06,255 --> 00:25:08,555 and know that sort of stuff and, and 478 00:25:08,555 --> 00:25:08,875 heavier 479 00:25:09,069 --> 00:25:10,709 Evan Troxel: be in it every single day. 480 00:25:10,719 --> 00:25:11,069 Right? 481 00:25:11,069 --> 00:25:11,309 Like 482 00:25:11,465 --> 00:25:13,205 Marty Rozmanith: And I, I learned some pretty heavy math being a 483 00:25:13,285 --> 00:25:14,525 structural engineer, but you know, the, 484 00:25:14,649 --> 00:25:14,869 Evan Troxel: Mm. 485 00:25:15,285 --> 00:25:17,685 Marty Rozmanith: computer science guys have a whole different sort of field of 486 00:25:17,685 --> 00:25:20,045 math that they have to learn in order to do some of the stuff that they do. 487 00:25:20,065 --> 00:25:22,805 And that was not just not where I was schooled. 488 00:25:22,865 --> 00:25:27,405 So, um, when I got back into this, into technology as a consultant and then 489 00:25:27,405 --> 00:25:31,685 eventually back into software, it was more defining the product requirements. 490 00:25:31,805 --> 00:25:34,485 'cause I knew how a software engineer thought, and I knew how 491 00:25:34,525 --> 00:25:35,645 a design professional thought. 492 00:25:35,665 --> 00:25:39,645 And so my real skill was being able to translate one set of vocabulary to 493 00:25:39,645 --> 00:25:43,045 the other set of vocabulary so that, you know, the, the software engineer 494 00:25:43,045 --> 00:25:46,485 would understand the problem they were trying to solve, and be able to talk to 495 00:25:46,705 --> 00:25:50,645 the designer and understand, you know, this is what I really needed to do as 496 00:25:50,725 --> 00:25:54,565 a, there are people who tell you what they want, but your job is to figure 497 00:25:54,565 --> 00:25:55,805 out what it is they actually need. 498 00:25:56,194 --> 00:25:56,614 Evan Troxel: Mm-Hmm. 499 00:25:57,105 --> 00:25:59,125 Marty Rozmanith: you know, what was it, Henry Ford said if I 500 00:25:59,125 --> 00:26:00,965 asked people what they wanted, they would've set a faster horse. 501 00:26:01,095 --> 00:26:01,445 Right? 502 00:26:01,505 --> 00:26:03,365 So, so the, the art of it is. 503 00:26:04,185 --> 00:26:09,110 Understanding how to take the input and then morph it into determining what 504 00:26:09,110 --> 00:26:12,950 the actual underlying needs and root causes of that request are, so that 505 00:26:12,950 --> 00:26:14,390 you can then turn that into something 506 00:26:15,969 --> 00:26:19,629 Evan Troxel: I'm, I'm, I'm interested in the Charles River early Revit days. 507 00:26:19,629 --> 00:26:22,949 Just from the standpoint of like, what were you inspired by? 508 00:26:22,949 --> 00:26:27,949 Because I know there was a few other, or maybe just a couple others BIM tools at 509 00:26:27,949 --> 00:26:32,269 that point, but was it really, I mean, did you have the foresight to kind of 510 00:26:32,279 --> 00:26:37,469 understand what the potential of what you were doing was, and, and were there 511 00:26:37,469 --> 00:26:41,709 other examples or were you really just solving the customer's problems, trying 512 00:26:41,729 --> 00:26:46,669 to pull that out of them to define what, what the things were that they 513 00:26:46,869 --> 00:26:48,469 actually needed to practice efficiently? 514 00:26:49,737 --> 00:26:51,937 Marty Rozmanith: I thought what we did at Architectural Desktop was quite a 515 00:26:51,937 --> 00:26:56,337 significant development in, in software because we got away from Lions, 516 00:26:56,337 --> 00:26:59,497 arks, and circles, and we had objects that were actually representing real 517 00:26:59,497 --> 00:27:01,057 world things as far as Waldo window. 518 00:27:01,436 --> 00:27:01,726 Evan Troxel: Yeah, 519 00:27:02,077 --> 00:27:03,937 Marty Rozmanith: Um, the thing about that piece of software that 520 00:27:03,937 --> 00:27:11,377 it was pretty by the infrastructure of AutoCAD that it was built on. 521 00:27:11,597 --> 00:27:16,897 So, um, the, the software RD team did as great of a job as it could by 522 00:27:17,097 --> 00:27:20,617 building this entire infrastructure called object, ARX, uh, that 523 00:27:20,617 --> 00:27:22,017 would enable these things to work. 524 00:27:22,277 --> 00:27:30,737 But it was, um, purely speaking, kind of clunky and the workflow of AutoCAD where 525 00:27:30,737 --> 00:27:37,257 you had to basically do one floor at a time in files that, um, you know, there 526 00:27:37,257 --> 00:27:39,017 was an entire XF structure around that. 527 00:27:39,186 --> 00:27:39,606 Evan Troxel: mm-Hmm? 528 00:27:40,337 --> 00:27:42,797 Marty Rozmanith: Uh, meant that you had to do a lot of pre-planning 529 00:27:42,817 --> 00:27:44,677 before you ever did any design work. 530 00:27:45,097 --> 00:27:50,877 Um, and so one of the things I recognized when, when I saw Revit was that that 531 00:27:50,897 --> 00:27:56,753 entire, presupposition of having to do things one floor at a time and having 532 00:27:57,013 --> 00:28:01,833 an X-ref structure and all those things that were sort of the computer side of 533 00:28:01,843 --> 00:28:05,953 using an AutoCAD based solutions didn't exist in Revit because it was just a clean 534 00:28:06,893 --> 00:28:09,923 Clean page rewrite of a building modeler. 535 00:28:10,463 --> 00:28:14,283 Um, and in fact, the branding of Revit was not Bim, BIM was something Autodesk 536 00:28:14,443 --> 00:28:18,203 invented as a marketing concept, but the branding of Revit was the world's 537 00:28:18,203 --> 00:28:19,523 first parametric building modeler. 538 00:28:19,523 --> 00:28:22,203 And what parametric went was something up for debate. 539 00:28:22,343 --> 00:28:27,043 Um, uh, parametric in our view was the change engine that allowed it to 540 00:28:27,043 --> 00:28:30,003 coordinate construction drawings, whereas most people now think of parametric 541 00:28:30,003 --> 00:28:34,483 in terms of shape generation like Grasshopper or Dynamo or things like that. 542 00:28:34,583 --> 00:28:37,083 But they're both valid definitions of parametric. 543 00:28:37,143 --> 00:28:42,363 But, um, the Revit parametric engine has more to do around coordinating sheets 544 00:28:42,553 --> 00:28:46,243 than it does, than it does geometry. 545 00:28:46,243 --> 00:28:51,723 And of course, um, you know, after I left, uh, I think the, the, the people 546 00:28:51,723 --> 00:28:55,203 who became product managers who were all very interested in shape generation 547 00:28:55,583 --> 00:28:59,843 put those sorts of things in there because, um, the market wanted it. 548 00:29:00,343 --> 00:29:03,883 So now b it does both, it does shape generation and the coordination of sheets. 549 00:29:03,943 --> 00:29:04,483 But, um. 550 00:29:06,018 --> 00:29:11,628 In the early days, the, the, the first part was that you could design a 551 00:29:11,748 --> 00:29:16,428 building and you didn't have to pre-plan how you were gonna organize the data 552 00:29:17,178 --> 00:29:20,068 just to make the computer serve your 553 00:29:20,068 --> 00:29:20,348 purpose. 554 00:29:20,447 --> 00:29:20,867 Evan Troxel: mm-Hmm. 555 00:29:21,048 --> 00:29:22,268 Marty Rozmanith: So that was the first thing I saw. 556 00:29:22,368 --> 00:29:25,108 The second thing, which was my real big concern, 'cause I was working 557 00:29:25,328 --> 00:29:29,708 at that point for the number one product, being pretty well paid and 558 00:29:29,708 --> 00:29:37,668 having, you know, I don't know, 50,000 users was how is this small team, um. 559 00:29:39,228 --> 00:29:42,568 Who obviously have some bright people not just gonna get crushed 560 00:29:42,568 --> 00:29:44,008 by a behemoth like Autodesk. 561 00:29:44,008 --> 00:29:48,328 And, and it was the CEO that they had just hired said to me, uh, big 562 00:29:48,568 --> 00:29:51,448 companies are just structurally incapable of doing certain things, right. 563 00:29:51,548 --> 00:29:55,488 We just basically we're gonna outrun them because we can just develop faster. 564 00:29:55,987 --> 00:29:56,407 Evan Troxel: mm-Hmm. 565 00:29:56,608 --> 00:29:58,488 Marty Rozmanith: is exactly basically what happened. 566 00:29:58,748 --> 00:30:04,968 Um, it was that, um, you didn't have to support the legacy infrastructure 567 00:30:05,348 --> 00:30:08,688 of a solution that was driving whatever, a billion dollars of revenue, 568 00:30:08,718 --> 00:30:09,728 half a billion dollars of revenue. 569 00:30:10,228 --> 00:30:12,568 And so you could just move a lot faster 'cause you didn't have any of 570 00:30:12,568 --> 00:30:13,648 those considerations to deal with. 571 00:30:13,668 --> 00:30:17,008 And so I just learned a lot about startup companies from the 572 00:30:17,168 --> 00:30:18,088 original Revit founding team. 573 00:30:18,108 --> 00:30:22,048 It was a fantastic team, not just the RD team that wrote the code, 574 00:30:22,148 --> 00:30:25,968 but the client support team and the marketing team and the sales team and, 575 00:30:25,988 --> 00:30:27,648 and the executive leadership team. 576 00:30:27,668 --> 00:30:30,688 It was just an entirely fantastic team on, on all sides. 577 00:30:31,108 --> 00:30:32,408 It was a great place to learn about it. 578 00:30:32,802 --> 00:30:33,902 Evan Troxel: In what year was that? 579 00:30:34,142 --> 00:30:34,702 I mean, what? 580 00:30:34,702 --> 00:30:36,022 This is like pre Revit 581 00:30:36,028 --> 00:30:38,838 Marty Rozmanith: Yeah, I, I joined in the summer of 1999 582 00:30:39,302 --> 00:30:39,592 Evan Troxel: Okay. 583 00:30:40,388 --> 00:30:43,008 Marty Rozmanith: and I was employee 26 and I think Dave Lamont was employee 584 00:30:43,008 --> 00:30:45,728 number 25 . Um, who was the CEO? 585 00:30:45,988 --> 00:30:50,608 So, um, and the, the two founders, uh, Lena and Irwin, they had 586 00:30:50,608 --> 00:30:55,448 started the year before, um, with a space above a pizza shop. 587 00:30:55,628 --> 00:30:57,848 Uh, so I wasn't in the space above the pizza shop. 588 00:30:57,888 --> 00:30:59,288 I didn't quite even know where that was. 589 00:30:59,388 --> 00:31:04,928 But, uh, we were in the, the Pink Palace in Framingham, and then we soon moved to 590 00:31:04,928 --> 00:31:08,008 wall fame after that, because we started, we started hiring people really fast. 591 00:31:08,828 --> 00:31:13,128 Um, 'cause once, once the customer started showing up, then you 592 00:31:13,408 --> 00:31:15,488 have to, you have to respond, 593 00:31:15,757 --> 00:31:17,217 Evan Troxel: you gotta deliver it. 594 00:31:17,237 --> 00:31:19,777 It, just to put this in context from my, from my point of 595 00:31:19,777 --> 00:31:21,817 view, I graduated college in 97 596 00:31:22,517 --> 00:31:28,497 and so I had used AutoCAD at least 12 or 14 maybe, and three D face 597 00:31:28,577 --> 00:31:29,937 commands to learn three D modeling. 598 00:31:30,037 --> 00:31:33,577 And I had, we actually had a Form Z lab, so that was where I 599 00:31:33,577 --> 00:31:37,937 was, I wasn't in the building information modeling database world at all. 600 00:31:37,997 --> 00:31:38,217 It 601 00:31:38,217 --> 00:31:39,657 was still very much file-based. 602 00:31:40,117 --> 00:31:42,937 And this whole x-ref thing that you're talking about, like the whole point 603 00:31:42,937 --> 00:31:45,537 of that is so that multiple people can work on a project at the same time. 604 00:31:45,547 --> 00:31:45,897 Right? 605 00:31:46,417 --> 00:31:49,457 'cause of course you could CAD the whole thing in one file if you wanted 606 00:31:49,457 --> 00:31:50,617 to lose it all at once, I guess. 607 00:31:50,877 --> 00:31:56,437 But, uh, the whole point of that was so that you could Have the elevations 608 00:31:56,437 --> 00:31:59,877 over here and the plans over here, and the sections over here, and people in 609 00:31:59,877 --> 00:32:01,237 the office could be working on those. 610 00:32:01,337 --> 00:32:03,357 And, and I guess assembling the sheets 611 00:32:03,868 --> 00:32:04,158 Marty Rozmanith: Yeah. 612 00:32:04,397 --> 00:32:08,357 Evan Troxel: happened via, you know, this really cool dynamic system of X-refs. 613 00:32:08,417 --> 00:32:11,997 Uh, and, and so there was like that AutoCAD world and then to me 614 00:32:11,997 --> 00:32:13,957 it was very separate working in 615 00:32:14,277 --> 00:32:14,517 three 616 00:32:14,597 --> 00:32:14,717 D. 617 00:32:14,808 --> 00:32:15,448 Marty Rozmanith: were very separate. 618 00:32:15,548 --> 00:32:19,448 You had designers who worked in three D modeling ish stuff like Form Z, and then 619 00:32:19,448 --> 00:32:23,728 you had production people who, who made the drawings that they got paid for and 620 00:32:23,728 --> 00:32:25,848 that, and that took a lot of pre-planning. 621 00:32:26,328 --> 00:32:26,448 Planning. 622 00:32:26,468 --> 00:32:29,088 You had a CAD manager, right, who figured out how the whole 623 00:32:29,088 --> 00:32:29,928 thing had to hang together 624 00:32:30,628 --> 00:32:34,248 and, and every job had a job captain who just figured out what is the 625 00:32:34,248 --> 00:32:37,808 sheet set and what do we have to do from a file standpoint to make 626 00:32:37,808 --> 00:32:41,748 that sheet set plot at the end of the day on a, on a plotter, right? 627 00:32:42,187 --> 00:32:46,057 Evan Troxel: Which, and and this is still happening in Revit, like there's still 628 00:32:46,057 --> 00:32:50,017 this huge discussion at the beginning of every project of how are we going to 629 00:32:50,957 --> 00:32:54,357 Assemble this, is it gonna be every building's in a separate file? 630 00:32:54,537 --> 00:32:57,277 Are we gonna have, you know, like what, there's, there's 631 00:32:57,277 --> 00:32:59,037 still a lot of time spent trying 632 00:32:59,037 --> 00:33:01,277 to figure that out, and I know this is something that, that you guys 633 00:33:01,297 --> 00:33:03,957 are, are going to be solving as well. 634 00:33:03,957 --> 00:33:07,757 Because this this has, the thinking has shifted and that, like, this isn't the 635 00:33:07,757 --> 00:33:11,997 kind of thing we should be spending a ton of time on every single project still 636 00:33:12,047 --> 00:33:16,317 hours and hours, and then switching it, sometimes midstream because something 637 00:33:16,317 --> 00:33:20,677 changes on the project and it, it is still quite a, a bear to deal with, I think. 638 00:33:21,633 --> 00:33:21,923 Marty Rozmanith: Yeah. 639 00:33:21,943 --> 00:33:25,803 You know, one of the things that I did, um, early in my career 640 00:33:25,823 --> 00:33:28,963 in San Francisco was we, uh, the architecture firm I was working for 641 00:33:29,623 --> 00:33:33,123 had, um, United Airlines as a client. 642 00:33:33,663 --> 00:33:38,843 And when the international terminal at SFO kicked off United called us and 643 00:33:38,843 --> 00:33:45,103 said, we know we have a lot of space at San Francisco Airport, we have no 644 00:33:45,103 --> 00:33:47,263 idea how much it is or where it is. 645 00:33:48,123 --> 00:33:51,823 So I got this field survey, , I got the field survey, San 646 00:33:51,823 --> 00:33:54,183 Francisco Airport, and, um. 647 00:33:55,338 --> 00:33:56,898 , you know, that takes a long time. 648 00:33:57,918 --> 00:34:03,858 Um, and put it all into AutoCAD, uh, just to be able to show them where all the 649 00:34:03,858 --> 00:34:09,538 space they had was, um, which was, you know, it was, you know, in the days before 650 00:34:09,538 --> 00:34:11,098 they were highly security conscious. 651 00:34:11,138 --> 00:34:13,898 I still had the palm scanner in order to be able to walk out on 652 00:34:13,898 --> 00:34:17,458 the tarmac and, you know, measure the outside of the, of the airport. 653 00:34:18,398 --> 00:34:21,098 But I eventually put together a set of AutoCAD files that showed that 654 00:34:21,098 --> 00:34:22,818 they had 2 million square feet, 655 00:34:23,822 --> 00:34:24,042 Evan Troxel: Wow. 656 00:34:24,958 --> 00:34:28,338 Marty Rozmanith: And, um, so then there was this plan of, with the international 657 00:34:28,818 --> 00:34:32,338 terminal coming online, how they were going to take all of those people 658 00:34:32,518 --> 00:34:34,178 and move a bunch of them over there. 659 00:34:34,197 --> 00:34:36,458 And then what space they were gonna keep, what space they were gonna get rid of. 660 00:34:36,458 --> 00:34:39,297 It was massive, like move, add changes problem. 661 00:34:40,358 --> 00:34:44,737 And there was nobody who had the appetite for trying to figure out 662 00:34:44,797 --> 00:34:46,378 how to do this with hand drawings. 663 00:34:46,378 --> 00:34:48,938 They were like, how are you gonna do this using AutoCAD? 664 00:34:49,438 --> 00:34:53,737 And so what I ended up doing was I ended up taking a, an access database and. 665 00:34:55,038 --> 00:34:59,408 Kind of a rough facility management system, connecting it to AutoCAD. 666 00:35:00,268 --> 00:35:04,688 And I would literally print a color book like that thick every 667 00:35:04,688 --> 00:35:07,848 week with just everything they had decided to do with the space. 668 00:35:07,988 --> 00:35:12,168 And so it was like an, it was a, it was a massive publishing job every 669 00:35:12,168 --> 00:35:16,208 week just to put out 2 million square feet of SFO space for United Airlines. 670 00:35:16,788 --> 00:35:19,848 And so that really got me to the understanding of what it's 671 00:35:19,848 --> 00:35:22,368 like for a database to drive a drawing production system. 672 00:35:22,662 --> 00:35:22,882 Evan Troxel: Mm. 673 00:35:23,503 --> 00:35:27,123 Marty Rozmanith: And the reason that I wanted to go work for Autodesk 674 00:35:27,123 --> 00:35:30,803 when they made me the job offer was that I, you know, up until that 675 00:35:30,803 --> 00:35:33,723 point, production of drawings and design were very separate things. 676 00:35:33,723 --> 00:35:36,883 And I saw Architectural Desktop as really the first place where 677 00:35:36,883 --> 00:35:40,243 you might be able to do design and production in the same system. 678 00:35:40,903 --> 00:35:45,203 And then I ran into a lot of that, you know, the, the presuppositions 679 00:35:45,203 --> 00:35:47,403 of AutoCAD, which designers didn't wanna have to deal with. 680 00:35:48,143 --> 00:35:52,123 Um, so then when I saw Revit, I said, oh, well this is even more in the direction 681 00:35:52,123 --> 00:35:55,203 of someplace where we might be able to do design and production in one system. 682 00:35:55,823 --> 00:35:58,843 And I think it's just been constantly trying to get to that point where, 'cause 683 00:35:58,843 --> 00:36:03,843 what I would like to be able to do is design production and then construction. 684 00:36:04,248 --> 00:36:08,588 All in one system, , that, that's where I, you know, the thesis I wrote back 685 00:36:08,588 --> 00:36:12,668 in 89 was around connecting design to construction so that all of that 686 00:36:12,668 --> 00:36:14,068 data can inform the means and methods. 687 00:36:14,248 --> 00:36:17,588 Not knowing anything about the fact that an architect is a special kinda lawyer 688 00:36:17,888 --> 00:36:21,108 and that you don't have insurance that covers anything after the deliverables 689 00:36:21,108 --> 00:36:24,588 and you can't inform means of methods, otherwise you're open to get lawsuits. 690 00:36:24,588 --> 00:36:29,588 And so there's been very interesting business, uh, you know, having the part 691 00:36:29,588 --> 00:36:33,508 of, part of the, the good of having the MBA is now, I understand all of the 692 00:36:33,508 --> 00:36:36,028 things that prevented this from happening weren't actually technical things at all. 693 00:36:36,028 --> 00:36:37,028 They were all legal things, 694 00:36:37,327 --> 00:36:37,527 Evan Troxel: Yeah. 695 00:36:37,637 --> 00:36:37,927 Yeah, 696 00:36:38,158 --> 00:36:39,988 Marty Rozmanith: legal and insurance constraints that, 697 00:36:39,988 --> 00:36:41,188 that caused that from happening. 698 00:36:41,928 --> 00:36:46,508 And spending 10 years at DESO systems looking at how OEMs do cars or airplanes 699 00:36:46,528 --> 00:36:52,588 or elevators or industrial equipment like Caterpillar, um, you see that it's 700 00:36:52,588 --> 00:36:55,188 just a totally different organization because manufacturing's only about 701 00:36:55,228 --> 00:36:56,228 a, you know, a hundred years old. 702 00:36:58,293 --> 00:37:01,353 The law predates manufacturing, well, like construction's 703 00:37:01,353 --> 00:37:02,633 like thousands of years old. 704 00:37:02,693 --> 00:37:03,753 It predates the law. 705 00:37:03,773 --> 00:37:08,833 And so the law in some ways was developed based on construction practices. 706 00:37:08,853 --> 00:37:11,913 And what you find is actually that construction practices 707 00:37:11,913 --> 00:37:15,033 are the same wherever you have English common law countries. 708 00:37:15,813 --> 00:37:20,313 And then in other places like France or other places where they have different 709 00:37:20,343 --> 00:37:23,233 laws, you actually have different construction practices because the two 710 00:37:23,253 --> 00:37:25,353 are sort of inextricable from one another. 711 00:37:25,933 --> 00:37:29,233 And so we actually have interesting things that go on in countries that are 712 00:37:29,233 --> 00:37:33,633 not based on English common law because now technology is not the constraint. 713 00:37:33,633 --> 00:37:36,993 And if law and insurances in those places, they're different law and insurance. 714 00:37:37,093 --> 00:37:38,953 And so you can actually learn from those places. 715 00:37:39,213 --> 00:37:41,353 So it's been a fascinating one. 716 00:37:41,353 --> 00:37:45,633 One of the things the So Systems did for me was it gave me a platform to see 717 00:37:45,633 --> 00:37:49,673 these differences worldwide that you wouldn't really be able to easily see if 718 00:37:49,673 --> 00:37:51,113 you were working for a smaller company. 719 00:37:51,892 --> 00:37:52,182 Evan Troxel: Yeah. 720 00:37:53,868 --> 00:37:57,198 Marty Rozmanith: That, that, that's been, uh, great for informing 721 00:37:57,338 --> 00:38:00,508 what's going on now with, with what we're doing with Skema. 722 00:38:01,732 --> 00:38:05,352 Evan Troxel: Uh, a friend of mine, friend of the show, Clifton Harness from Test 723 00:38:05,372 --> 00:38:08,992 Fit, he, he said, if you want to be innovative in, in architecture 724 00:38:08,992 --> 00:38:11,632 or in technology, he said, you start with the OAC C contract. 725 00:38:11,632 --> 00:38:11,832 Right? 726 00:38:11,832 --> 00:38:16,072 Start with the owner architect agreement, because, so, so much of what 727 00:38:16,072 --> 00:38:19,192 we do is based on that, and there's 728 00:38:19,192 --> 00:38:21,352 only so much we can do because of that. 729 00:38:21,362 --> 00:38:21,712 Right? 730 00:38:21,812 --> 00:38:25,312 Uh, I, I think that what you're saying is, is right in line with 731 00:38:25,312 --> 00:38:26,632 that and, and it's incredible. 732 00:38:27,822 --> 00:38:33,112 Insurance law contracts, like all of these things, permitting agencies, 733 00:38:33,652 --> 00:38:37,312 uh, it's still based on printing. 734 00:38:37,462 --> 00:38:38,312 It's still based on that 735 00:38:38,432 --> 00:38:38,872 PDF, 736 00:38:39,098 --> 00:38:40,188 Marty Rozmanith: It's based on the artifact. 737 00:38:40,972 --> 00:38:41,192 Evan Troxel: yep. 738 00:38:41,248 --> 00:38:45,308 Marty Rozmanith: And this is one of the things I learned from having tried 739 00:38:45,308 --> 00:38:48,828 these manufacturing companies and seeing how the OEMs do it from my time 740 00:38:48,828 --> 00:38:52,668 at the, so is that ? In every other industry other than construction, 741 00:38:54,748 --> 00:38:58,178 there are process engineers who have process diagrams of the way things 742 00:38:58,178 --> 00:39:01,378 happen at an automotive manufacturer or at an aircraft manufacturer. 743 00:39:01,998 --> 00:39:05,898 And in fact, those process engineers have conventions just like other professionals, 744 00:39:05,898 --> 00:39:08,738 and they compare their process diagrams to other people, process diagrams. 745 00:39:08,738 --> 00:39:11,938 And eventually, after 20 years, the industry comes up with a best practices 746 00:39:11,938 --> 00:39:15,938 process diagram for standard operating procedure for an automotive plant 747 00:39:15,998 --> 00:39:17,658 or a aircraft plant or whatever. 748 00:39:17,918 --> 00:39:20,498 So you can literally go to a consultant and say, what is the best 749 00:39:20,898 --> 00:39:22,538 practice process for an aircraft? 750 00:39:23,078 --> 00:39:23,938 And they can tell you, 751 00:39:24,412 --> 00:39:24,702 Evan Troxel: Yeah. 752 00:39:25,198 --> 00:39:26,788 Marty Rozmanith: and nobody in AAC can, 753 00:39:27,232 --> 00:39:27,522 Evan Troxel: Nope. 754 00:39:28,178 --> 00:39:30,158 Marty Rozmanith: uh, I'm probably one of the only people who's ever 755 00:39:30,158 --> 00:39:34,838 tried to diagram using BPMN five, design and construction process. 756 00:39:35,178 --> 00:39:37,238 And it's an impossible problem because what happens 757 00:39:37,382 --> 00:39:38,372 Evan Troxel: Every project's different. 758 00:39:38,588 --> 00:39:41,038 Marty Rozmanith: Depending if you're doing a hospital, you've got 759 00:39:41,038 --> 00:39:43,598 medical gas consultants and you've got a whole bunch of piping that 760 00:39:43,598 --> 00:39:44,718 doesn't exist in any other building. 761 00:39:44,718 --> 00:39:46,078 And so the scope is totally different. 762 00:39:46,078 --> 00:39:49,558 If I'm doing an airport, I've got a baggage handling consultant who knows 763 00:39:49,558 --> 00:39:52,078 all about conveying systems, and those are all completely different. 764 00:39:52,098 --> 00:39:56,838 And so the scope, the contract, and the team changes depending 765 00:39:56,838 --> 00:40:00,158 on the type of project and the process changes with the team. 766 00:40:00,858 --> 00:40:04,918 And so it's very, very difficult to use any process-based system 767 00:40:04,918 --> 00:40:06,878 like PLM in manufacturing to 768 00:40:06,878 --> 00:40:07,078 try 769 00:40:07,112 --> 00:40:07,332 Evan Troxel: Mm. 770 00:40:07,538 --> 00:40:09,918 Marty Rozmanith: the construction process because that's just 771 00:40:09,918 --> 00:40:10,958 not how it's organized. 772 00:40:11,018 --> 00:40:14,558 And um, you know, part of what I learned from comparing 773 00:40:14,558 --> 00:40:15,958 the two is that really what. 774 00:40:17,008 --> 00:40:18,508 A's organized around is artifacts. 775 00:40:18,608 --> 00:40:21,348 You know, architects will make an artifact and then they'll go back and 776 00:40:21,348 --> 00:40:22,308 say, what worked, what didn't work? 777 00:40:22,338 --> 00:40:23,828 Okay, on the next one, let's not do this. 778 00:40:23,838 --> 00:40:24,748 Let's do this instead. 779 00:40:24,748 --> 00:40:25,468 And then they learn. 780 00:40:25,468 --> 00:40:29,788 They learn from artifact to artifact, which is we literally directly 781 00:40:29,788 --> 00:40:33,188 implementing that into Skema where you take this old Revit stuff that you've 782 00:40:33,188 --> 00:40:34,188 been sitting there doing nothing. 783 00:40:34,448 --> 00:40:37,308 And we learn from that and put it into the new project. 784 00:40:37,448 --> 00:40:38,708 So it's just a lot easier to use. 785 00:40:39,648 --> 00:40:44,008 And, know, anybody who comes from manufacturing will always think of, 786 00:40:44,118 --> 00:40:47,568 okay, how do I, they they always start with process first and try and 787 00:40:47,568 --> 00:40:51,688 impose process and realize after a while that's not how it works here. 788 00:40:52,502 --> 00:40:52,622 Evan Troxel: I, 789 00:40:52,692 --> 00:40:53,542 I've had that exact 790 00:40:53,542 --> 00:40:54,382 same experience. 791 00:40:54,698 --> 00:40:57,108 Marty Rozmanith: It's, it's, it's just fundamentally different. 792 00:40:57,362 --> 00:40:57,652 Evan Troxel: Yeah. 793 00:40:57,812 --> 00:41:01,812 A, a guy that I worked with on a project out of San Francisco at Project Frog, 794 00:41:02,232 --> 00:41:07,372 we were doing some prefabricated school stuff, and this guy, Ash, he had come 795 00:41:07,372 --> 00:41:13,452 from automotive and he, it was like three years into Project Frog, and he was still 796 00:41:13,452 --> 00:41:15,812 like, I cannot believe how hard this is. 797 00:41:15,972 --> 00:41:18,732 I, it, he thought, he thought it would just directly apply. 798 00:41:18,912 --> 00:41:19,292 He thought 799 00:41:19,292 --> 00:41:21,172 they were gonna, they were just gonna figure it out. 800 00:41:21,712 --> 00:41:25,732 and and to your point, it was just like impossible to figure out because 801 00:41:25,732 --> 00:41:30,092 every project is a different set of rules, constraints, uh, team 802 00:41:30,092 --> 00:41:33,132 members, inputs, outputs, all, it's all different all the time. 803 00:41:34,603 --> 00:41:37,903 Marty Rozmanith: And so there, there is a way to learn from manufacturing, 804 00:41:38,083 --> 00:41:42,983 but it is not by the, by replicating the process they use to make things. 805 00:41:44,053 --> 00:41:51,603 It's rather, um, you can productize pieces of construction and then use that to 806 00:41:51,603 --> 00:41:53,363 make overall construction more efficient. 807 00:41:53,363 --> 00:41:55,083 Like a great example is an elevator, right? 808 00:41:55,103 --> 00:41:58,163 An elevator is a manufactured product, yet it's different for every building. 809 00:41:58,403 --> 00:42:00,683 'cause every building has a different number of floors, a 810 00:42:00,683 --> 00:42:02,883 different floor to floor height, a different structural system. 811 00:42:03,103 --> 00:42:06,083 And yet somehow they manage to manufacture an elevator on schedule 812 00:42:06,103 --> 00:42:07,683 and install it and maintain it. 813 00:42:08,077 --> 00:42:08,427 Evan Troxel: Right. 814 00:42:08,623 --> 00:42:09,443 Marty Rozmanith: Um, and 815 00:42:09,443 --> 00:42:09,643 there 816 00:42:09,707 --> 00:42:11,307 Evan Troxel: they are, but they are always broken. 817 00:42:11,307 --> 00:42:11,627 Marty. 818 00:42:11,817 --> 00:42:12,347 Well, I'll just 819 00:42:12,347 --> 00:42:12,587 say that. 820 00:42:12,718 --> 00:42:13,638 Marty Rozmanith: it's, yeah, yeah. 821 00:42:14,568 --> 00:42:17,278 There are certain companies trying to apply that, you know, specified 822 00:42:17,278 --> 00:42:18,918 and delivered by owner principle 823 00:42:19,087 --> 00:42:19,507 Evan Troxel: Mm-Hmm. 824 00:42:19,948 --> 00:42:23,638 Marty Rozmanith: certain very time sensitive, um, buildings, like data 825 00:42:23,638 --> 00:42:27,278 centers, like just don't, don't bother the contractor with assembling the 826 00:42:27,278 --> 00:42:28,878 guts of a data center will do ourselves 827 00:42:29,137 --> 00:42:29,557 Evan Troxel: Mm-Hmm. 828 00:42:29,857 --> 00:42:30,277 .Mm-Hmm. 829 00:42:30,338 --> 00:42:34,238 Marty Rozmanith: Um, but you know, McKinsey and so all the, especially 830 00:42:34,238 --> 00:42:37,078 the so systems, they took notice of this, McKinsey wrote a report on 831 00:42:37,678 --> 00:42:40,798 construction heading towards modular, and they said 25% of the value chain 832 00:42:40,798 --> 00:42:44,518 of construction is gonna move towards modular, which is in many hundreds of 833 00:42:44,518 --> 00:42:45,918 billions of dollars of work in place. 834 00:42:46,858 --> 00:42:51,698 And I think, you know, um, finance people saw that and said, oh, 835 00:42:52,218 --> 00:42:53,378 construction's turning modular. 836 00:42:53,448 --> 00:42:55,378 There's a huge disruptive opportunity. 837 00:42:55,508 --> 00:42:56,418 Let's get in the game. 838 00:42:56,838 --> 00:42:58,538 And that's when you saw all of these like. 839 00:42:59,543 --> 00:43:03,883 AI driven configurators doing massing based on developer proforma pop up, right? 840 00:43:03,903 --> 00:43:06,003 And all of a sudden they were just gonna come up with a feasibility 841 00:43:06,003 --> 00:43:10,043 study and we apply some modules and boom, we have a end-to-end solution. 842 00:43:10,783 --> 00:43:15,763 And I see that, and I say to myself, McKinsey might be right, but that doesn't 843 00:43:15,763 --> 00:43:18,763 mean construction projects are gonna be a hundred percent modular anytime soon. 844 00:43:19,033 --> 00:43:23,193 Like you can look at a hotel, like what Marriott's doing 845 00:43:23,193 --> 00:43:24,513 with bathroom pods, right? 846 00:43:24,613 --> 00:43:27,433 And the, the hotel is still engineered order, but now all the 847 00:43:27,593 --> 00:43:29,993 bathroom pods are modulars that they're shipping as units, right? 848 00:43:30,733 --> 00:43:34,753 Or, or unitized facade or, or even kitchen pods or things like that. 849 00:43:35,633 --> 00:43:38,033 I see that as modular penetrates. 850 00:43:38,093 --> 00:43:43,033 The construction value chain projects are gonna go from 0% modular to 20% modular 851 00:43:43,053 --> 00:43:46,233 to 30% modular to maybe 40% modular. 852 00:43:47,293 --> 00:43:50,353 But you know, the most advanced work I've seen in modular and 853 00:43:50,553 --> 00:43:54,353 construction, other than very simple buildings is like 70% modular. 854 00:43:54,998 --> 00:43:57,578 Uh, because every time you gotta interface with the ground, it's not 855 00:43:57,578 --> 00:44:02,538 gonna be modular anyway, so, so I see this, and, and part of the reason that 856 00:44:02,578 --> 00:44:07,618 I decided to make Skema in the fir, you know, leave my fairly comfortable 857 00:44:07,618 --> 00:44:11,298 job at DESO Systems and go ride the wild bucking bronco of a startup again, 858 00:44:11,687 --> 00:44:12,037 Evan Troxel: Uhhuh, 859 00:44:12,318 --> 00:44:15,598 Marty Rozmanith: was the fact that I didn't wanna see a world 860 00:44:15,598 --> 00:44:18,798 where the engineer to order stuff was, was done in Revit. 861 00:44:18,798 --> 00:44:22,398 And then there was this other system that dealt with the 30% modular stuff. 862 00:44:22,558 --> 00:44:26,278 I was like, designers will lose their minds if they have to design half 863 00:44:26,278 --> 00:44:29,238 the building here and then half the building here, and then try and figure 864 00:44:29,238 --> 00:44:30,558 out, out all fits together somehow. 865 00:44:31,618 --> 00:44:37,038 Um, and so that's part of the, that's part of the, the, the motivation for taking 866 00:44:37,038 --> 00:44:42,078 this on at this point, which is I see what's coming from a execution standpoint 867 00:44:42,338 --> 00:44:46,598 and designers can't directly get ahead of means and methods, but the systems 868 00:44:46,978 --> 00:44:48,718 can evolve so that they don't have to. 869 00:44:49,642 --> 00:44:49,762 Evan Troxel: Hmm. 870 00:44:51,142 --> 00:44:52,402 The perfect segue. 871 00:44:52,702 --> 00:44:55,882 It is time to stop bearing the lead and talk about Skema here. 872 00:44:55,982 --> 00:44:56,762 So I. 873 00:44:57,322 --> 00:45:00,822 By the time this episode comes out, it will have been November 1st. 874 00:45:00,872 --> 00:45:01,342 It'll be 875 00:45:01,342 --> 00:45:02,822 past your, your release date. 876 00:45:02,882 --> 00:45:06,422 So give us an idea of what Skema is. 877 00:45:06,642 --> 00:45:09,622 So like, just let, let's start on the outside and work our way in. 878 00:45:09,993 --> 00:45:10,213 Marty Rozmanith: Yep. 879 00:45:10,692 --> 00:45:12,102 Evan Troxel: Tell us what Skema is. 880 00:45:12,202 --> 00:45:16,022 You, you mentioned that, that you, you've moved from de so into Skema 881 00:45:16,042 --> 00:45:18,942 and you didn't think that you would get back on the wild bucking Bronco. 882 00:45:18,962 --> 00:45:23,902 So tell us kind of what, what was the spark there and, and what is so exciting 883 00:45:23,902 --> 00:45:25,342 about the work that you're doing now? 884 00:45:25,342 --> 00:45:26,702 What's, what's the potential here? 885 00:45:29,703 --> 00:45:30,873 Marty Rozmanith: Yeah, so I guess I'll tell you. 886 00:45:33,113 --> 00:45:34,893 How I became aware of the technology team. 887 00:45:34,913 --> 00:45:40,533 So these, these guys in Eastern European, Eastern Europe had written this really 888 00:45:40,533 --> 00:45:44,373 bunch of prototype code libraries for doing modular residential production. 889 00:45:44,632 --> 00:45:44,712 Evan Troxel: Hmm. 890 00:45:45,353 --> 00:45:48,453 Marty Rozmanith: Um, and so they had written configurators, uh, 891 00:45:48,603 --> 00:45:50,053 different types of configurators. 892 00:45:50,053 --> 00:45:57,083 They had written some for apartment buildings, some of them for, um, uh, 893 00:45:57,433 --> 00:46:01,483 mass timber office buildings, uh, some of them for parking garages. 894 00:46:01,483 --> 00:46:06,723 They had their, their, their, just had this competency in writing configurators 895 00:46:06,913 --> 00:46:08,723 that dealt with manufactured systems. 896 00:46:09,183 --> 00:46:12,203 And so they were trying to figure out a way to bring some of this 897 00:46:12,203 --> 00:46:15,203 technology to market, but they didn't, you know, they had good technology. 898 00:46:15,383 --> 00:46:20,963 And, and the, the, the most amazing thing about this technical team was that they. 899 00:46:23,243 --> 00:46:28,543 Didn't write this on somebody else's tech stack, like Forge or, or something else. 900 00:46:28,853 --> 00:46:32,303 They wrote all of their own math, just like the original Revit team did. 901 00:46:32,303 --> 00:46:35,183 The, the original Revit team had to write its own three D engine, 902 00:46:35,243 --> 00:46:37,983 its own constraints, solvers, its own, all of this stuff, right? 903 00:46:38,163 --> 00:46:44,103 So the entire tech stack was written by that original Revit team, um, which is 904 00:46:44,103 --> 00:46:48,063 why in some cases Revit was so weird about what kind of surfaces it could do because 905 00:46:48,133 --> 00:46:49,583 they wrote their own surfacing engine. 906 00:46:50,523 --> 00:46:57,203 Um, and so this team wrote all of its own tech stack and they, they decided 907 00:46:57,203 --> 00:47:00,163 that the ultimate manifestation of the tech stack was these configurators. 908 00:47:01,753 --> 00:47:07,323 Well, one of the things I decided to do, um, leaving deso systems was that I was 909 00:47:07,323 --> 00:47:09,243 gonna see if I could pioneer a way of. 910 00:47:09,813 --> 00:47:14,778 Showing this change in construction that was coming towards modular and ended up 911 00:47:14,908 --> 00:47:18,818 going in with, with a friend of mine who was also a licensed architect and had 912 00:47:18,818 --> 00:47:23,218 done some commercial property development on a, uh, multi-family commercial 913 00:47:23,368 --> 00:47:25,538 apartment project in Massachusetts. 914 00:47:26,358 --> 00:47:29,578 And we had talked about, you know, doing things that most owners wouldn't 915 00:47:29,578 --> 00:47:35,378 be willing to do and doing this in a, for, uh, affordable housing, not 916 00:47:35,378 --> 00:47:39,178 by making them cheap, but by using modular delivery to drive down the 917 00:47:39,378 --> 00:47:44,418 delivery cost of the facility so that we could, um, produce housing. 918 00:47:44,418 --> 00:47:44,858 Housing. 919 00:47:44,918 --> 00:47:47,898 It wasn't affordable housing, it was just housing that was affordable, which 920 00:47:47,898 --> 00:47:49,938 in Massachusetts is almost impossible. 921 00:47:50,502 --> 00:47:50,792 Evan Troxel: Okay. 922 00:47:51,068 --> 00:47:53,018 Marty Rozmanith: right, because our rent structure is the same as. 923 00:47:53,713 --> 00:47:55,733 San Francisco or all the other big tech places. 924 00:47:56,873 --> 00:48:01,533 And so we said, alright, we'll do this as a project because we understand 925 00:48:01,673 --> 00:48:05,533 design and construction, and this is just a good thing to do to show 926 00:48:05,533 --> 00:48:07,773 this as a, as a, as a project. 927 00:48:08,393 --> 00:48:10,533 But we also wanna use it as a test beds for software. 928 00:48:10,753 --> 00:48:14,893 And so after I left, you know, the, these various configurators that came 929 00:48:14,893 --> 00:48:20,013 out, all the ones that were done by private equities since about 2017, 930 00:48:20,313 --> 00:48:26,133 uh, the Archie Stars of the world, the delves, the, um, you know, Spacemaker, 931 00:48:26,133 --> 00:48:27,333 which was bought by Autodesk. 932 00:48:27,333 --> 00:48:31,453 All, all these configurators that come up with a, a project feasibility analysis. 933 00:48:31,533 --> 00:48:35,853 I wanted to say, you know, as someone who's designing a project on a real world 934 00:48:35,853 --> 00:48:39,813 site that has slope differences and has, you know, a podium that has mixed uses 935 00:48:39,813 --> 00:48:43,613 like parking and commercial, and then residents above, could I actually use 936 00:48:43,613 --> 00:48:44,893 one of these things to do a real project? 937 00:48:45,113 --> 00:48:47,973 And I, we applied a bunch of them and none of them worked. 938 00:48:49,393 --> 00:48:52,693 And so we actually had, uh, we hired an architect out of Boston. 939 00:48:53,948 --> 00:48:57,168 And after we went through these experiments, um, he ended up doing it in 940 00:48:57,178 --> 00:49:01,408 Rhino . So we reached out to some of these tech companies and we were like, look, 941 00:49:01,708 --> 00:49:05,168 we tried to use our system on this actual project and here's why it didn't work. 942 00:49:05,308 --> 00:49:08,928 But we, you know, basically recorded the charette we did in Zoom and we'll send 943 00:49:08,928 --> 00:49:13,288 you a copy of it so you can see how we actually did it, you know, and, uh, these 944 00:49:13,288 --> 00:49:19,688 guys, um, that had developed what is now SSkemagot back to me and, and said, uh. 945 00:49:20,683 --> 00:49:22,053 Okay, uh, let us work on it. 946 00:49:22,073 --> 00:49:24,493 And so, you know, I don't know, several weeks later they were like, 947 00:49:24,493 --> 00:49:25,413 Hey, can we have a Zoom meeting? 948 00:49:25,433 --> 00:49:27,613 So I, I had a Zoom meeting and they're like, we, we, we did it. 949 00:49:27,613 --> 00:49:28,493 We wrote what you wanted. 950 00:49:29,393 --> 00:49:30,253 I'm like, what are talking about? 951 00:49:30,393 --> 00:49:35,053 So they showed me this thing, which, which was called Skema, uh, which was basically, 952 00:49:35,833 --> 00:49:40,933 uh, some implementation of, of the ideas of, you know, solving this multi-family 953 00:49:41,003 --> 00:49:46,093 project in, um, in Massachusetts using their residential configurator. 954 00:49:46,093 --> 00:49:49,053 But now with this, easier to use front end on the front of it, but all the 955 00:49:49,053 --> 00:49:51,853 backend hard math was all the stuff that they had written in the past. 956 00:49:52,553 --> 00:49:56,573 And I had, I actually put this, uh, company on the desso, uh, mergers 957 00:49:56,573 --> 00:50:00,293 and acquisitions team roadmap, but a couple years passed and 958 00:50:00,293 --> 00:50:01,573 decided, decided not to do anything. 959 00:50:01,573 --> 00:50:04,533 And so I thought to myself, well, if these guys actually have a way 960 00:50:04,533 --> 00:50:07,813 of solving this problem that might make a good piece of software, 961 00:50:08,593 --> 00:50:08,973 and so. 962 00:50:11,768 --> 00:50:14,848 Probably half a year after I left a set of systems, I started talking to these guys 963 00:50:14,848 --> 00:50:19,408 about doing a, doing a deal where I set up a company to acquire the technology. 964 00:50:19,568 --> 00:50:21,648 'cause we know we, we have an idea of how to take this to 965 00:50:21,648 --> 00:50:23,608 market and uh, let's do that. 966 00:50:23,628 --> 00:50:24,568 And so that's what we did. 967 00:50:24,868 --> 00:50:28,608 And we signed an agreement with them at the end of last year and started working 968 00:50:28,668 --> 00:50:31,008 on adjusting the roadmap in the spring. 969 00:50:31,868 --> 00:50:35,328 Uh, and essentially launched it at the a i A show in June where 970 00:50:35,328 --> 00:50:36,808 people got to get their hands on it. 971 00:50:37,468 --> 00:50:42,448 Uh, but at that time it was still very modular, so it was very much a 972 00:50:43,278 --> 00:50:46,128 modular configurator for apartment buildings and that's what it could do. 973 00:50:46,368 --> 00:50:50,128 'cause that's basically what the original prototype code they had written was. 974 00:50:52,128 --> 00:50:57,748 Um, what we're coming out with by the time this airs is all the work that 975 00:50:57,748 --> 00:51:00,628 we've done with architects over the last six months to take that idea of 976 00:51:00,668 --> 00:51:03,468 a modular configurator that can make apartment buildings and turn it into 977 00:51:03,468 --> 00:51:07,148 something that is far more general that can apply to all buildings. 978 00:51:07,208 --> 00:51:14,958 And so, in short, what Skema is, is a conceptual design system that can learn 979 00:51:14,958 --> 00:51:18,798 from your previous Revit projects using the layouts for things like, let's say 980 00:51:18,798 --> 00:51:23,958 you're doing a healthcare facility and you have exam suites and labs and surgery 981 00:51:24,138 --> 00:51:26,078 suites in previous Revit projects. 982 00:51:26,898 --> 00:51:29,558 It can farm those things out of the rabbit projects. 983 00:51:30,673 --> 00:51:32,573 And put them into a concept catalog. 984 00:51:32,833 --> 00:51:36,533 So then when you're trying to resolve the part T of that healthcare facility, 985 00:51:37,393 --> 00:51:42,333 um, you can much more easily at a sort of jello cube moving things around 986 00:51:42,333 --> 00:51:44,893 level, um, solve the, the Part T. 987 00:51:44,953 --> 00:51:49,013 And then because we know what Revit data it came from, we can generate the 988 00:51:49,023 --> 00:51:53,293 Revit model out of it without you having to take the two intervening months to 989 00:51:53,573 --> 00:51:57,653 manually model Waldo window to represent what those gel cubes are in Revit. 990 00:51:58,833 --> 00:52:04,373 Um, and so the idea there is that from a, from a metaphor standpoint, you're 991 00:52:04,373 --> 00:52:06,013 bumping up one level from wall's. 992 00:52:06,013 --> 00:52:10,373 Door was windows to working with whole chunks of buildings as the way an 993 00:52:10,373 --> 00:52:11,933 architect would think about the program. 994 00:52:13,073 --> 00:52:16,533 Um, so I almost call it meta bim, um, in that I'm not 995 00:52:16,533 --> 00:52:17,573 doing BIM at the object level. 996 00:52:17,673 --> 00:52:20,053 I'm not doing it at the whole chunks of building level, but the 997 00:52:20,053 --> 00:52:21,413 chunks are things that you've done. 998 00:52:22,518 --> 00:52:25,238 Previously, uh, that we're reusing in a systematic way. 999 00:52:25,578 --> 00:52:28,158 And so what's interesting about this is that we give you a conceptual design 1000 00:52:28,158 --> 00:52:31,198 environment where you create a mass and then you start applying these 1001 00:52:31,198 --> 00:52:32,798 catalogs to do the block and stack. 1002 00:52:34,648 --> 00:52:37,628 But even if we had an architect that started out on the same site with 1003 00:52:37,628 --> 00:52:41,668 the same mass, their catalogs look totally different because the data 1004 00:52:41,668 --> 00:52:43,228 in the Revit projects is different. 1005 00:52:43,288 --> 00:52:47,068 So once they generate the Revit models, you know, architect one is gonna have 1006 00:52:47,068 --> 00:52:50,348 their wall styles and their doors and their windows and their furniture 1007 00:52:50,348 --> 00:52:54,268 fixtures, equipment lighting, all of that stuff that comes from their 1008 00:52:54,268 --> 00:52:57,628 catalog of work is what appears in their Revit model for that project 1009 00:52:57,628 --> 00:53:01,428 versus the architect two, their catalog of stuff is completely different. 1010 00:53:01,448 --> 00:53:06,068 So what's interesting about this process and this um, systemization 1011 00:53:06,208 --> 00:53:09,508 of the design process is that you don't lose the individuality of 1012 00:53:09,508 --> 00:53:14,028 the architects, the buildings that result look like what that architect. 1013 00:53:15,788 --> 00:53:17,598 Because it came from their ingredients. 1014 00:53:18,138 --> 00:53:21,278 And now that, um, some of the architects that we've been doing charettes with 1015 00:53:21,278 --> 00:53:24,598 and have been putting this on project realize, you know, they can basically 1016 00:53:24,598 --> 00:53:27,318 resolve a whole bunch of the building and then they can start having design 1017 00:53:27,598 --> 00:53:30,878 exercises separately on facade and how they want the building to look and, you 1018 00:53:30,878 --> 00:53:33,918 know, so they can resolve form and they can resolve function and then they can 1019 00:53:33,918 --> 00:53:37,598 get into variations of that, uh, to serve. 1020 00:53:38,018 --> 00:53:38,238 Um. 1021 00:53:39,918 --> 00:53:43,698 How they want the building to feel from the outside and the inside experientially. 1022 00:53:43,698 --> 00:53:47,418 And part of what we're trying to do is our goal is never to make a hundred percent 1023 00:53:47,698 --> 00:53:51,498 complete building our, we, we describe our ourselves as a fast forward button, 1024 00:53:51,718 --> 00:53:54,898 uh, with the, with the idea that we're the fastest way to get to 60% complete. 1025 00:53:55,478 --> 00:53:56,778 So that would take you two months. 1026 00:53:57,198 --> 00:53:58,138 We can do it in two minutes. 1027 00:53:59,118 --> 00:54:02,298 Um, and then you just take the result of that and do what you normally would 1028 00:54:02,558 --> 00:54:06,218 as an architect In Revit, it's just, we take a lot of the boring stuff that you 1029 00:54:06,218 --> 00:54:10,338 have to manually do out of it so that if you have all of the things that are 1030 00:54:10,338 --> 00:54:14,378 experiential about the building, the entry, um, in some cases in a healthcare 1031 00:54:14,618 --> 00:54:17,458 facility, the signature waiting area that's multi height and you know, got 1032 00:54:17,458 --> 00:54:18,858 all sorts of interesting things going on. 1033 00:54:18,858 --> 00:54:21,378 That's where you spend your time as an architect, not on laying 1034 00:54:21,398 --> 00:54:23,858 out patient rooms and labs. 1035 00:54:24,797 --> 00:54:25,877 Evan Troxel: Starting over every, yeah. 1036 00:54:26,057 --> 00:54:28,837 So I'm gonna, my marketing brain is going in and so Mark, 1037 00:54:29,107 --> 00:54:30,677 what is your zero to 60 time? 1038 00:54:32,368 --> 00:54:33,138 Marty Rozmanith: Zero to 60. 1039 00:54:33,457 --> 00:54:34,507 Evan Troxel: Zero to 60%. 1040 00:54:34,507 --> 00:54:35,307 Like you, that's your 1041 00:54:35,307 --> 00:54:35,667 goal, right? 1042 00:54:35,667 --> 00:54:36,507 The fast forward button. 1043 00:54:36,507 --> 00:54:38,187 So what you, what is your zero to 60 time? 1044 00:54:38,187 --> 00:54:38,387 What? 1045 00:54:38,387 --> 00:54:40,267 What does that actually look like for somebody who's using 1046 00:54:40,867 --> 00:54:42,227 a tool like Skema or using 1047 00:54:42,533 --> 00:54:47,623 Marty Rozmanith: Yeah, so we typically, I mean the, the the, we have a very risky 1048 00:54:47,813 --> 00:54:49,623 marketing and sales approach in that. 1049 00:54:49,803 --> 00:54:52,903 Um, I've worked for many, many large, large software companies 1050 00:54:52,903 --> 00:54:54,983 that will do death by PowerPoint. 1051 00:54:55,763 --> 00:54:59,423 Uh, we typically will do one of those just to get people to understand 1052 00:54:59,423 --> 00:55:00,583 what we're talking about on Zoom. 1053 00:55:00,763 --> 00:55:06,063 But, uh, our typical approach is we sign an NDA because we're gonna 1054 00:55:06,063 --> 00:55:09,023 have the architect send us their Revit models for anything that we're 1055 00:55:09,023 --> 00:55:10,543 gonna use in a charette with them. 1056 00:55:10,613 --> 00:55:13,063 They have to send us two or three Revit models of that project type. 1057 00:55:13,063 --> 00:55:16,223 So it's not like we're getting a big data lake with thousands of Revit 1058 00:55:16,223 --> 00:55:17,823 models and training it on something. 1059 00:55:17,823 --> 00:55:19,263 We, we need two or three rev models. 1060 00:55:20,123 --> 00:55:23,263 And then, um, from that we will go into their office. 1061 00:55:23,493 --> 00:55:27,203 They will invite people who've never seen Skema, 1062 00:55:27,983 --> 00:55:31,273 will make the accounts the first half hour of the meeting after 1063 00:55:31,293 --> 00:55:32,433 we, they introduce themselves. 1064 00:55:33,403 --> 00:55:34,768 We'll teach 'em how to use it in an hour. 1065 00:55:35,348 --> 00:55:39,758 Um, two hours later they will have a building in Revit, uh, 1066 00:55:39,768 --> 00:55:40,958 which they didn't think was 1067 00:55:41,358 --> 00:55:43,638 possible before they walked in the room that day. 1068 00:55:43,698 --> 00:55:49,318 And so that's generally, I mean, that's our biggest hurdle is, is convincing 1069 00:55:49,318 --> 00:55:51,758 people that what we're talking about is not magic science fiction in the future. 1070 00:55:51,758 --> 00:55:54,238 That it's actually here and that, that you can actually use 1071 00:55:54,238 --> 00:55:55,198 it right now if you want to. 1072 00:55:56,018 --> 00:55:59,318 Um, so our zero to 60 time is about three hours. 1073 00:56:00,037 --> 00:56:00,257 Evan Troxel: Wow. 1074 00:56:01,197 --> 00:56:08,017 It, it's gotta be really satisfying to you to watch those people's aha. 1075 00:56:08,017 --> 00:56:08,257 Moment. 1076 00:56:08,507 --> 00:56:08,857 Right. 1077 00:56:08,997 --> 00:56:12,417 And, and what, what is that like as a, you know, this goes back 1078 00:56:12,417 --> 00:56:13,857 to your early days when you wrote 1079 00:56:13,877 --> 00:56:15,457 the the thing for your mom, right? 1080 00:56:15,477 --> 00:56:20,097 And it was like that when you saw 10 people using this tool that you had made. 1081 00:56:20,557 --> 00:56:25,977 And in this case, again, like achieving the, what seems to be impossible for most 1082 00:56:25,977 --> 00:56:27,377 people to comprehend. 1083 00:56:27,607 --> 00:56:30,137 Like, what is that, what's that like for you? 1084 00:56:31,168 --> 00:56:33,588 Marty Rozmanith: Uh, it is interesting and there's a lot of different 1085 00:56:33,588 --> 00:56:34,788 flavors of those aha moments. 1086 00:56:35,128 --> 00:56:35,348 Uh, 1087 00:56:35,757 --> 00:56:36,837 Evan Troxel: Storming out of the room? 1088 00:56:36,837 --> 00:56:37,717 People just pissed 1089 00:56:37,777 --> 00:56:37,997 off. 1090 00:56:38,428 --> 00:56:41,468 Marty Rozmanith: I mean, some, some people are like, holy crap, AI's 1091 00:56:41,468 --> 00:56:45,548 coming, uh, but other, other people, you know, and, and what we, when we 1092 00:56:45,548 --> 00:56:49,228 hold one of these charettes, we like to mix senior people and junior people. 1093 00:56:49,278 --> 00:56:53,028 We've had people who are senior because, you know, a lot of the people, we 1094 00:56:53,028 --> 00:56:55,628 have a conceptual environment, design environment that does options, right? 1095 00:56:55,628 --> 00:56:58,748 So it is made to do presentations, to win work. 1096 00:56:59,608 --> 00:57:02,868 Um, and a lot of the, your senior people are the ones going after 1097 00:57:02,868 --> 00:57:05,308 those projects and they're losing two out of three projects because 1098 00:57:05,308 --> 00:57:06,548 that's the win ratio, right? 1099 00:57:06,648 --> 00:57:08,708 And so they're spending a lot of their time at risk. 1100 00:57:09,968 --> 00:57:12,748 Um, so we've had senior people like that come in. 1101 00:57:12,748 --> 00:57:14,988 They don't, they don't, certainly don't use Revit. 1102 00:57:15,128 --> 00:57:17,748 Um, but some of them don't even use SketchUp. 1103 00:57:17,748 --> 00:57:21,203 And they've used this thing and they . And two, two hours later they got a building. 1104 00:57:22,023 --> 00:57:26,763 Um, that, that quickness of wind gives them confidence that 1105 00:57:27,073 --> 00:57:28,443 this is not for other people. 1106 00:57:28,473 --> 00:57:29,723 This I can actually do it. 1107 00:57:30,423 --> 00:57:33,883 Um, so that aha moment is, is different 'cause that can sometimes 1108 00:57:33,943 --> 00:57:34,883 be a little scary for them. 1109 00:57:35,043 --> 00:57:37,483 'cause they've never, you know, they've always done everything on trace, right? 1110 00:57:37,623 --> 00:57:40,323 So that's, that's, that's one level of aha moment. 1111 00:57:40,383 --> 00:57:43,603 The other one is, uh, the junior people in the room, right? 1112 00:57:43,603 --> 00:57:46,363 So senior and junior people in, in this type of charette. 1113 00:57:47,383 --> 00:57:51,083 Uh, when we first came out with Revit, it was interesting that, uh, a lot of 1114 00:57:51,083 --> 00:57:53,963 people, like we, at the beginning of this call we talked about, you know, the people 1115 00:57:53,963 --> 00:57:56,003 doing production with x-refs and AutoCAD. 1116 00:57:56,143 --> 00:58:02,563 And at that time, you know, in the 99 2000, when you show somebody 1117 00:58:02,653 --> 00:58:06,643 Revit, they're pigeonholed doing production on AutoCAD 10 hours a day 1118 00:58:06,783 --> 00:58:08,243 and they see this Revit thing and go. 1119 00:58:08,738 --> 00:58:10,868 This is my way outta being pigeonholed in AutoCAD. 1120 00:58:11,208 --> 00:58:13,388 And what's interesting about the aha moment for these junior 1121 00:58:14,038 --> 00:58:17,668 staff, uh, in these firms is they see this and they go, wait, this 1122 00:58:17,668 --> 00:58:18,948 can do my Revit production work. 1123 00:58:18,978 --> 00:58:21,908 This is a way for me to get out of being pigeonholed in Revit 1124 00:58:21,908 --> 00:58:23,868 doing production work, and now I can do more interesting things. 1125 00:58:23,888 --> 00:58:27,868 So it's just the parallelism between those two, uh, was, that's one of 1126 00:58:28,028 --> 00:58:29,108 the biggest surprises actually. 1127 00:58:29,228 --> 00:58:33,028 I had not, uh, anticipated that, uh, that that's just come 1128 00:58:33,028 --> 00:58:36,228 out of seeing the reactions of people and using it on projects. 1129 00:58:37,442 --> 00:58:39,762 Evan Troxel: let's talk about what it's like to actually work in Skema. 1130 00:58:39,782 --> 00:58:45,192 What you showed me was, I, I loved it because I, we've built 1131 00:58:45,192 --> 00:58:46,272 scripts that have done this, 1132 00:58:46,332 --> 00:58:47,832 and it was arduous process. 1133 00:58:48,332 --> 00:58:51,152 Uh, so what you're doing makes, everything that I've done in the 1134 00:58:51,152 --> 00:58:52,272 past seem completely obsolete. 1135 00:58:52,272 --> 00:58:56,912 But the idea of just drawing a, a line of circulation and you pick 1136 00:58:56,952 --> 00:58:58,392 a site, it's got a slope to it. 1137 00:58:58,392 --> 00:59:00,192 It's got, uh, contextual buildings. 1138 00:59:00,532 --> 00:59:02,992 So you've got kind of an environmental aspect to this thing. 1139 00:59:03,262 --> 00:59:07,552 Obviously, sites aren't, a building site is not in a vacuum. 1140 00:59:07,812 --> 00:59:12,432 You, you need context, but you, you start off with this very simple concept 1141 00:59:12,612 --> 00:59:16,192 of circulation and the kind of the double loaded corridor condition, 1142 00:59:16,772 --> 00:59:22,647 and then Uh, based on the architect's kind of library catalog of spaces that 1143 00:59:22,647 --> 00:59:27,687 you mentioned earlier, you then kind of built the blocking and stacking based 1144 00:59:27,747 --> 00:59:33,447 on a very simple version of those, and it automatically kind of populates and 1145 00:59:33,447 --> 00:59:34,367 then you start to move things around. 1146 00:59:34,527 --> 00:59:38,167 I, this was a very dumb version of what you explained. 1147 00:59:38,267 --> 00:59:39,847 I'm sure you can explain it much better. 1148 00:59:39,907 --> 00:59:42,127 So talk about what it's actually like to use the tool. 1149 00:59:44,718 --> 00:59:46,768 Marty Rozmanith: Yeah, it's, it's interesting because I've, you 1150 00:59:46,768 --> 00:59:49,848 know, architectural Desktop had a massing tool and a, and a spaces 1151 00:59:50,078 --> 00:59:52,088 tool, and Revit has a massing tool. 1152 00:59:52,908 --> 00:59:57,648 Um, so this is, you know, and, and I that we had one called building 1153 00:59:57,648 --> 00:59:58,808 space Planning at the systems. 1154 00:59:58,828 --> 01:00:02,928 So this is like my fourth time around on massing and space layout tools. 1155 01:00:03,748 --> 01:00:03,968 Um. 1156 01:00:06,088 --> 01:00:10,468 The thing about Skema is that it's extremely fast and flexible, kind 1157 01:00:10,468 --> 01:00:14,508 of like SketchUp, but it's not just about making faces and shapes. 1158 01:00:14,968 --> 01:00:17,588 So the idea is you start with a site context, right? 1159 01:00:17,588 --> 01:00:21,388 With the surrounding buildings and all of the things that you have to consider and 1160 01:00:21,408 --> 01:00:26,428 at, and you, you basically start out by blocking mass and you don't know whether 1161 01:00:26,448 --> 01:00:28,388 the mass you have is big enough or not. 1162 01:00:28,448 --> 01:00:32,468 You've just got some rules of thumb based on whatever brief you have, uh, about 1163 01:00:32,468 --> 01:00:36,308 where the building should be on the site based on, you know, sight lines, sun 1164 01:00:36,518 --> 01:00:38,948 views, noise, whatever your criterion is. 1165 01:00:40,368 --> 01:00:44,188 But once you get to, you know, you might do three or four different massing 1166 01:00:44,188 --> 01:00:45,948 options just to try different things. 1167 01:00:46,648 --> 01:00:50,548 Um, within each of those massing object o uh, options, you're gonna assign 1168 01:00:50,958 --> 01:00:55,668 space usage so that you can, from an analytics standpoint, see how much of 1169 01:00:55,668 --> 01:00:58,868 each use do I have, do I have enough of each use based on the brief that I got? 1170 01:00:59,568 --> 01:01:01,508 Um, how can I solve the 1171 01:01:01,508 --> 01:01:01,708 brief 1172 01:01:01,837 --> 01:01:02,257 Evan Troxel: Mm-Hmm. 1173 01:01:03,108 --> 01:01:04,308 Marty Rozmanith: creatively on this site? 1174 01:01:04,838 --> 01:01:05,318 Several 1175 01:01:05,318 --> 01:01:05,638 different 1176 01:01:05,647 --> 01:01:06,067 Evan Troxel: Mm-Hmm. 1177 01:01:06,583 --> 01:01:10,003 Marty Rozmanith: Um, and once you get to that point where you have things roughly 1178 01:01:10,483 --> 01:01:16,523 sized, both from a mass and space use standpoint, you can get into simulation. 1179 01:01:16,523 --> 01:01:20,203 So you can look at sun, you can look at daylight, you can look at those factors 1180 01:01:20,583 --> 01:01:26,043 to say, oh, this mass doesn't work 'cause I'm, I'm blocking all of the sun access to 1181 01:01:26,043 --> 01:01:32,643 this adjacent property, um, day lighting's bad in this condition because of whatever 1182 01:01:32,643 --> 01:01:34,083 other feature I have in my context. 1183 01:01:34,743 --> 01:01:37,243 So you can make, you can rule out some of your massing options. 1184 01:01:37,853 --> 01:01:39,633 Uh, based on just some simulation. 1185 01:01:40,373 --> 01:01:44,513 And we expect that to just get more robust as time goes on, because 1186 01:01:44,713 --> 01:01:47,473 simulation's just one of these things in conceptual design being plugged in. 1187 01:01:47,553 --> 01:01:51,513 I mean, if you look at form, form has a dozen different simulation 1188 01:01:51,513 --> 01:01:54,193 engines for everything from wind to noise to whatever you want. 1189 01:01:55,053 --> 01:01:58,153 Um, and then once you, you know, once you get down to a couple 1190 01:01:58,153 --> 01:02:01,033 different options, that's when you've gotta see if it's feasible. 1191 01:02:01,033 --> 01:02:03,113 And that's when you really try and fit the proforma in. 1192 01:02:03,133 --> 01:02:05,993 By doing the blocking, stacking and figuring out the Part T for the building, 1193 01:02:06,733 --> 01:02:11,593 that's where we really shine because that's when we can actually help just 1194 01:02:12,033 --> 01:02:16,593 starting with circulation and exiting, then fitting in the parts of the program 1195 01:02:16,783 --> 01:02:18,273 that you need to fit into that mass. 1196 01:02:18,853 --> 01:02:21,433 And you don't have to do it in that order. 1197 01:02:21,813 --> 01:02:25,153 You can, you can go to the block and stack and realize, oh, I actually need 1198 01:02:25,153 --> 01:02:28,623 to change the mass and then just . , turn that off, change the mass around, 1199 01:02:28,623 --> 01:02:29,903 and then reapply, block and stack. 1200 01:02:29,923 --> 01:02:30,743 So it's iterative 1201 01:02:30,743 --> 01:02:30,903 in 1202 01:02:31,002 --> 01:02:31,742 Evan Troxel: Mm mm-Hmm. 1203 01:02:31,823 --> 01:02:32,623 Marty Rozmanith: not sequential. 1204 01:02:33,323 --> 01:02:36,423 It you can go in whatever order is, is useful to you. 1205 01:02:37,123 --> 01:02:41,463 Uh, but eventually what you end up with is a site context that has some mass 1206 01:02:41,463 --> 01:02:44,463 that you've worked out because you've simulated it and you, and, and it's 1207 01:02:44,463 --> 01:02:46,383 working from all of those simulations. 1208 01:02:46,883 --> 01:02:49,903 And you've resolved the brief as far as the Part T and the 1209 01:02:49,903 --> 01:02:51,063 block stack in that mass. 1210 01:02:51,763 --> 01:02:55,183 And then once you're at that condition, that's when you can just instantly go to 1211 01:02:55,253 --> 01:02:59,623 high LOD Revit data because everything that you've got there represents a 1212 01:02:59,623 --> 01:03:02,223 placeholder for chunks of buildings that we have in that catalog library 1213 01:03:02,223 --> 01:03:08,663 that can then reconstitute the building from that higher level, uh, met BIM type 1214 01:03:08,663 --> 01:03:10,663 of arrangement that you've developed. 1215 01:03:10,663 --> 01:03:13,903 So you don't have to think about the bim, you just, it ends up being a byproduct. 1216 01:03:14,973 --> 01:03:18,123 Of that conceptual design process that you've done in Skema. 1217 01:03:18,373 --> 01:03:20,713 And in fact for us, the two things are different systems. 1218 01:03:20,713 --> 01:03:25,513 Skema AI is the conceptual piece that you actually do all the conceptual work in. 1219 01:03:26,213 --> 01:03:31,043 And then once you have that resolved block and stack, that's what we use 1220 01:03:31,043 --> 01:03:34,403 in a backend system called Skema bim that actually generates the BIM data. 1221 01:03:34,423 --> 01:03:37,243 And what we do is we take that and preview it in Skema so you 1222 01:03:37,243 --> 01:03:38,003 can see what it looks like. 1223 01:03:38,423 --> 01:03:40,443 So you could say, oh, that's not what I was expecting. 1224 01:03:40,443 --> 01:03:43,883 And then you can turn that off, change the block and stack, or get rid of the 1225 01:03:43,883 --> 01:03:45,763 block and stack change the Mac reblock it. 1226 01:03:45,983 --> 01:03:48,843 So again, like the whole point of generating the BIM is so you have 1227 01:03:48,883 --> 01:03:52,163 a touch point of did this work the way I was expecting or did some 1228 01:03:52,213 --> 01:03:54,763 weird thing happened when I actually turned it back into a building? 1229 01:03:55,583 --> 01:03:58,603 But what's nice about that is in the current process, you would 1230 01:03:58,603 --> 01:04:01,123 only find that out after a couple months of painstaking work. 1231 01:04:01,153 --> 01:04:03,683 Like you would, you would get to the point and you'd be like, oh, I didn't like, 1232 01:04:03,683 --> 01:04:05,963 that's not what we should have done here. 1233 01:04:05,983 --> 01:04:08,243 You just get that answer in like a minute, minute and a half. 1234 01:04:08,303 --> 01:04:10,723 And then if you don't like it, you just go back and try something else. 1235 01:04:11,317 --> 01:04:13,847 Evan Troxel: Yeah, I was gonna bring that up because the, the, how much 1236 01:04:13,847 --> 01:04:18,047 time do we waste as a industry in that feedback loop right there. 1237 01:04:18,047 --> 01:04:18,367 Right, 1238 01:04:18,367 --> 01:04:22,927 Because it does take time to figure all of that out, to only find out 1239 01:04:22,927 --> 01:04:24,527 that, oh, that didn't actually work. 1240 01:04:24,867 --> 01:04:28,207 And so then you either have to decide to spend the time and do it again, 1241 01:04:28,787 --> 01:04:33,127 or you have to just say, uh, we're gonna try to figure that out later. 1242 01:04:33,137 --> 01:04:33,487 Right. 1243 01:04:33,507 --> 01:04:33,727 Or 1244 01:04:33,747 --> 01:04:34,327 as we go. 1245 01:04:34,377 --> 01:04:34,727 right. 1246 01:04:34,747 --> 01:04:37,647 and and that's bo both of those are, are painful decisions to 1247 01:04:37,647 --> 01:04:39,607 make, to have, to make if you didn't do it right the first time. 1248 01:04:41,208 --> 01:04:41,498 Marty Rozmanith: Yeah. 1249 01:04:41,498 --> 01:04:44,218 And I mean, design is an iterative process, so you're gonna go through that. 1250 01:04:44,408 --> 01:04:48,938 It's just, um, what is the easiest way to get to the best answer, 1251 01:04:49,278 --> 01:04:49,578 you know? 1252 01:04:49,678 --> 01:04:52,378 So that's what we're, that's what we're trying to deliver in, in this. 1253 01:04:52,678 --> 01:04:56,418 Um, and I, I, I honestly believe in two things with software and 1254 01:04:56,418 --> 01:04:59,218 that this is always applied for any software I've ever done. 1255 01:04:59,878 --> 01:05:02,338 Uh, the first is you have to meet the mirror mortals test. 1256 01:05:02,478 --> 01:05:05,338 So there's software that works, but normal humans can't use it. 1257 01:05:05,518 --> 01:05:07,458 And, and this is part of the problem with some of these things, 1258 01:05:07,458 --> 01:05:10,378 like Grasshopper is like that principle that doesn't use SketchUp. 1259 01:05:10,388 --> 01:05:12,018 She's not using Dynamo, right? 1260 01:05:12,758 --> 01:05:15,418 Um, so part of this is the mirror mortals test. 1261 01:05:15,478 --> 01:05:19,338 So a lot of what we do, we prototype in things like Grasshopper, but eventually 1262 01:05:20,038 --> 01:05:25,618 we want to take the 80 to 90% that really shouldn't, is the, is the common 1263 01:05:25,618 --> 01:05:26,978 thing that everybody needs to use. 1264 01:05:27,793 --> 01:05:28,693 Across the board. 1265 01:05:29,153 --> 01:05:31,813 And that goes into Skema, which is a web app where you don't have to 1266 01:05:31,813 --> 01:05:34,053 install anything and you can just use it straight outta the box. 1267 01:05:34,113 --> 01:05:37,973 And that's the mere mortals implementation as opposed to, say, a grasshopper 1268 01:05:37,973 --> 01:05:39,133 script that does the equivalent thing. 1269 01:05:39,133 --> 01:05:42,613 But it has a very fragile instantiation environment where you need the certain 1270 01:05:42,803 --> 01:05:45,773 plugins and all sorts of stuff to be in exactly the right place for it to work. 1271 01:05:46,713 --> 01:05:49,413 Um, we wanna be a web app where you don't have to think about any of that. 1272 01:05:49,413 --> 01:05:50,933 So that's the mere mortals test. 1273 01:05:51,313 --> 01:05:52,973 And then the other is the easy to use test. 1274 01:05:53,033 --> 01:05:55,493 If it's easier, people will use it, and that's it. 1275 01:05:56,993 --> 01:05:58,333 . If it's easier for 'em, they'll use it. 1276 01:05:58,333 --> 01:05:59,373 And if it's not, they won't. 1277 01:05:59,433 --> 01:06:03,693 And, uh, so mere mortals and easy, easy ease of use test, uh, that usually 1278 01:06:03,743 --> 01:06:06,413 leads you to the right answers from the standpoint of a software product. 1279 01:06:06,957 --> 01:06:09,737 Evan Troxel: It, it is pretty incredible that SketchUp got that so Right. 1280 01:06:10,377 --> 01:06:11,357 So long ago, right? 1281 01:06:11,357 --> 01:06:16,477 Because it, it, how many, how many ICON's in the UI are driving SketchUp that 1282 01:06:16,477 --> 01:06:17,877 most people use on a day-to-Day basis. 1283 01:06:18,027 --> 01:06:18,797 It's like five tools. 1284 01:06:19,096 --> 01:06:20,877 And those are the ones that are, are right there 1285 01:06:21,497 --> 01:06:22,677 and easy to use. 1286 01:06:22,857 --> 01:06:27,677 And is, of course, this is why it won so big in the industry. 1287 01:06:27,777 --> 01:06:32,917 So it's, it's kind of refreshing to hear that because yeah, software is 1288 01:06:33,197 --> 01:06:37,797 powerful, but if most people can't use it, then it's not gonna get adopted. 1289 01:06:37,977 --> 01:06:40,277 And I think that's, this is the hurdle that we have to overcome 1290 01:06:40,377 --> 01:06:45,037 as an industry, which is the, the ever increasing gap from innovation 1291 01:06:45,507 --> 01:06:47,157 between innovation and adoption. 1292 01:06:47,167 --> 01:06:47,517 Right? 1293 01:06:48,077 --> 01:06:49,557 Adoption is so difficult. 1294 01:06:50,107 --> 01:06:53,221 I've Led digital practice at a, at a large firm. 1295 01:06:53,962 --> 01:06:58,502 And adoption is so hard because the deadline of the current project is the 1296 01:06:58,502 --> 01:07:00,342 only thing that matters to most people. 1297 01:07:00,882 --> 01:07:02,221 And so when do I have time to learn? 1298 01:07:02,292 --> 01:07:06,062 When do I have time to try a new tool that maybe, or maybe isn't gonna work? 1299 01:07:06,602 --> 01:07:09,262 Uh, so it's, it's again, refreshing to hear this. 1300 01:07:09,282 --> 01:07:13,142 And I, I wanna reiterate what you just said about it being a web app. 1301 01:07:13,202 --> 01:07:17,422 Can you just kind of go around that, explain why you decided to 1302 01:07:17,572 --> 01:07:23,142 release Skema as a web app versus a on, you know, a workstation based 1303 01:07:23,282 --> 01:07:26,862 app or a, an installation based app, because I don't want it to. 1304 01:07:27,997 --> 01:07:28,857 Go unnoticed. 1305 01:07:29,157 --> 01:07:33,817 Uh, the, the major pros, obviously there are some cons, you have to be connected, 1306 01:07:34,237 --> 01:07:36,096 et cetera, so maybe you can talk through some of those. 1307 01:07:36,197 --> 01:07:40,137 But the whole idea of what you said about Grasshopper and making sure the scripts 1308 01:07:40,137 --> 01:07:43,137 are all installed on everybody's machine so that they can run the tools that 1309 01:07:43,137 --> 01:07:44,897 they need to do the feasibility study. 1310 01:07:44,897 --> 01:07:46,337 And like that, that's a 1311 01:07:46,617 --> 01:07:51,177 nightmare for a lot of CAD and BIM and it people to have to manage. 1312 01:07:51,717 --> 01:07:54,977 And if they don't have to manage that stuff with a piece of software as 1313 01:07:55,137 --> 01:07:59,497 powerful as this, I mean, that is another reason to take a serious look at it. 1314 01:08:00,273 --> 01:08:00,563 Marty Rozmanith: Yeah. 1315 01:08:00,563 --> 01:08:04,243 And, and we're not, um, we're not saying that people shouldn't do that because 1316 01:08:04,243 --> 01:08:08,003 they get a lot of value from making something that 10 people find useful. 1317 01:08:08,583 --> 01:08:13,363 So, you know, for us Skema, we haven't implemented it yet, but it's gonna be a 1318 01:08:13,363 --> 01:08:17,483 Grasshopper host so that you can take your facade script and actually generate it in 1319 01:08:17,483 --> 01:08:19,483 Skema, just like you would in Grasshopper. 1320 01:08:20,223 --> 01:08:24,403 Um, but for the 80% of the stuff that everybody needs to be able to use out of 1321 01:08:24,403 --> 01:08:28,803 the box, um, that'll be, that'll just be native in Skema so that people don't have 1322 01:08:28,803 --> 01:08:33,243 to understand how to instantiate it or what they need to do to get it to start. 1323 01:08:34,328 --> 01:08:36,068 so I, I'm not sure if that answered your 1324 01:08:36,229 --> 01:08:36,349 question. 1325 01:08:36,398 --> 01:08:38,888 Evan Troxel: Well, well just the, the cloud-based aspect of 1326 01:08:38,929 --> 01:08:39,219 Marty Rozmanith: Yeah. 1327 01:08:39,827 --> 01:08:41,247 Evan Troxel: why did you decide to go down that road? 1328 01:08:42,459 --> 01:08:44,309 Marty Rozmanith: Well, I think just because everything's headed there, 1329 01:08:44,689 --> 01:08:51,529 um, by doing this as a web app, we is, if my goal is to connect design to 1330 01:08:51,729 --> 01:08:55,129 construction, it's very difficult to do that in desktop based software, right? 1331 01:08:55,129 --> 01:09:01,836 Because, I see, uh, uh, a future where we have an ecosystem of 1332 01:09:01,836 --> 01:09:04,556 connected web apps that use web services to talk to each other. 1333 01:09:04,566 --> 01:09:09,876 We've done a few of those things just in Skema already, just to show this way, as 1334 01:09:09,876 --> 01:09:12,316 opposed to, and I'm not against platforms. 1335 01:09:12,386 --> 01:09:13,756 desa is a very powerful platform. 1336 01:09:13,776 --> 01:09:15,156 Auto's a very powerful platform. 1337 01:09:15,935 --> 01:09:22,716 Uh, but the idea of a platform as the guardian of your data is one approach to. 1338 01:09:23,866 --> 01:09:24,956 Putting things on the web. 1339 01:09:25,095 --> 01:09:29,156 The other is that you've got a series of apps, kinda like a peer-to-peer 1340 01:09:29,406 --> 01:09:30,556 where they can talk to each other. 1341 01:09:30,736 --> 01:09:32,156 And that's basically what we're doing. 1342 01:09:32,156 --> 01:09:35,756 So we've, for instance, on some of the simulation, we've done an integration 1343 01:09:35,756 --> 01:09:38,036 with Cove tool because people are used to some of the Cove tool. 1344 01:09:38,036 --> 01:09:40,116 Daylighting UIs and some of the other things that Cove tool does. 1345 01:09:40,116 --> 01:09:42,756 So we just did a direct scheme at a Cove tool integration. 1346 01:09:43,845 --> 01:09:47,356 We're doing, we're generating architectural BIM data, but when you 1347 01:09:47,356 --> 01:09:52,076 move from say, fully modular solutions, like what we had done previously to 1348 01:09:52,076 --> 01:09:56,196 things that combine engineer to order normal construction with modular pieces, 1349 01:09:56,816 --> 01:09:58,996 you need primary frame again, right? 1350 01:09:59,016 --> 01:09:59,676 To hold things up. 1351 01:09:59,736 --> 01:09:59,956 So. 1352 01:10:00,946 --> 01:10:04,486 Uh, we've done some work with Thornton Tomasetti to take the block and stack 1353 01:10:04,776 --> 01:10:10,726 cubes that generate the architectural scope in Revit to their Asterisk, um, 1354 01:10:11,236 --> 01:10:18,086 product that generates the structural scope, uh, BIM model at high LOD so 1355 01:10:18,086 --> 01:10:21,206 that we can generate both and that they actually come out pre-coordinated. 1356 01:10:21,226 --> 01:10:26,246 And then from those two models we can generate using other AI vendors, MEP 1357 01:10:26,246 --> 01:10:29,606 systems that are also pre-coordinated with the architecture and structure. 1358 01:10:29,706 --> 01:10:33,886 So I see that the, the ecosystem of connected web apps is going to be able 1359 01:10:33,886 --> 01:10:38,166 to solve things that have not been solvable in the desktop environment 1360 01:10:38,436 --> 01:10:38,856 Evan Troxel: Mm-Hmm. 1361 01:10:39,266 --> 01:10:42,846 Marty Rozmanith: and that, um, there's gonna be so much value unlocked 1362 01:10:42,846 --> 01:10:46,766 from that, that it'll be a massive structural advantage for those that 1363 01:10:46,766 --> 01:10:49,126 are, that are participating in that way. 1364 01:10:49,826 --> 01:10:53,126 And eventually, yet you, uh, if you really wanna impact construction, 1365 01:10:53,126 --> 01:10:57,606 you gotta, uh, you have to impact the actual construction delivery process. 1366 01:10:57,906 --> 01:10:58,126 So. 1367 01:10:59,316 --> 01:11:02,876 Starting from procurement all the way to how things get sourced and made 1368 01:11:02,876 --> 01:11:04,556 and delivered and installed on site. 1369 01:11:04,736 --> 01:11:10,596 So, um, to some extent, we'll we will systemize the front end of that so 1370 01:11:10,596 --> 01:11:13,596 that people can take advantage of that and systematize the backend. 1371 01:11:13,976 --> 01:11:17,516 We might also end up systematizing some of the backend things like procurement 1372 01:11:18,136 --> 01:11:21,436 and possibly even doing revenue share with designers so that they get some of 1373 01:11:21,436 --> 01:11:24,876 the benefits of having done the modeling work without having to take on the 1374 01:11:24,876 --> 01:11:28,476 liability of the means and method risks that they can't do because of insurance. 1375 01:11:28,656 --> 01:11:32,596 So there's, by doing this on the web, you open up a number of interesting business 1376 01:11:32,596 --> 01:11:37,996 opportunities and models that just are not feasible with desktop software. 1377 01:11:38,571 --> 01:11:40,871 Evan Troxel: and just thinking about it from a development standpoint and 1378 01:11:40,871 --> 01:11:46,151 releasing tools and bug fixes and updates, and how great is it when 1379 01:11:46,541 --> 01:11:50,071 it's so transparent that I don't even have to think about, uh, clicking a 1380 01:11:50,071 --> 01:11:51,311 button that might nuke my project? 1381 01:11:51,631 --> 01:11:53,311 I mean, it, it, I, I mean, you, 1382 01:11:53,311 --> 01:11:55,551 you take on that liability as the company, I guess, 1383 01:11:55,931 --> 01:11:59,111 but, but just that the new tools, it's always running 1384 01:11:59,131 --> 01:12:00,191 on the most current version. 1385 01:12:00,381 --> 01:12:03,471 This is also another nightmare for BIM managers 1386 01:12:03,931 --> 01:12:05,071 around the world, right? 1387 01:12:05,131 --> 01:12:05,711 Uh, which 1388 01:12:05,711 --> 01:12:09,391 is, how long do we keep it in that version is everybody on that version. 1389 01:12:09,851 --> 01:12:13,351 And just the amount of communication that has to happen around those 1390 01:12:13,351 --> 01:12:17,791 kind of decisions is incredible and and complete waste when you look 1391 01:12:17,791 --> 01:12:19,071 at it from the big picture. 1392 01:12:20,116 --> 01:12:22,296 Marty Rozmanith: What's in, and the other thing about this is, it's interesting 1393 01:12:22,296 --> 01:12:24,986 that this learns from your previous Revit projects, but once you have it 1394 01:12:24,986 --> 01:12:27,736 in is Skema catalog, you don't have to think about Revit versions anymore. 1395 01:12:28,861 --> 01:12:29,141 Evan Troxel: Interesting. 1396 01:12:29,206 --> 01:12:30,736 Marty Rozmanith: that that might make life a little easier. 1397 01:12:31,621 --> 01:12:34,401 Evan Troxel: One, one of the things that you showed was the, and you, 1398 01:12:34,421 --> 01:12:38,921 you talked about it here, is this idea of these catalog items getting 1399 01:12:38,921 --> 01:12:40,641 plugged into the Skema model. 1400 01:12:41,381 --> 01:12:42,561 How, how squishy are they? 1401 01:12:42,621 --> 01:12:46,001 Uh, because one of the questions I'm sure people have floating around in 1402 01:12:46,161 --> 01:12:52,181 their mind is, you know, different depth to width ratios and, and if the Skema 1403 01:12:52,201 --> 01:12:57,241 model is one thing, but my catalog item is another, you know, how, how does it 1404 01:12:57,541 --> 01:12:58,281 adjust for that? 1405 01:12:59,386 --> 01:13:01,406 Marty Rozmanith: So when we talk about the catalog, we're talking about, 1406 01:13:01,706 --> 01:13:07,496 um, knowledge encapsulated in a Revit artifact from a previous project. 1407 01:13:07,796 --> 01:13:11,536 So, you know, if I think about cad, like AutoCAD, that's data lines, 1408 01:13:11,566 --> 01:13:17,886 arcs and circles, and, and it goes data, information, knowledge, wisdom. 1409 01:13:18,306 --> 01:13:20,366 So data is lines, arcs, and circles. 1410 01:13:20,706 --> 01:13:23,686 Um, information is objects, walls, doors, windows. 1411 01:13:23,686 --> 01:13:25,486 That's why it's building information modeling. 1412 01:13:26,266 --> 01:13:27,606 And we're bumping it up to. 1413 01:13:28,496 --> 01:13:29,106 Knowledge. 1414 01:13:29,241 --> 01:13:32,741 So the knowledge is encapsulated with how that surgery suite was laid out 1415 01:13:32,801 --> 01:13:36,221 or how that exam suite is laid out. 1416 01:13:37,401 --> 01:13:40,941 Um, and we're pulling that into a concept catalog in Skema. 1417 01:13:40,961 --> 01:13:44,221 And then the main part of what is so big about the release that we're 1418 01:13:44,221 --> 01:13:48,501 putting out in November is that, um, you know, you lay out the circulation 1419 01:13:48,501 --> 01:13:52,061 and the exiting and then you can lay out things that are regular size 1420 01:13:52,111 --> 01:13:53,541 based on what you previously did. 1421 01:13:53,541 --> 01:13:56,941 But you will have leftover spaces that aren't the same size and shape. 1422 01:13:57,881 --> 01:14:01,621 And what Skema understands how to do is take the logic of the layout that 1423 01:14:01,621 --> 01:14:06,101 it has in the catalog and morph it into the target size and shape, respecting 1424 01:14:06,691 --> 01:14:09,061 minimum maximum distances in target areas. 1425 01:14:09,896 --> 01:14:11,076 To give you a workable layout. 1426 01:14:11,256 --> 01:14:14,716 Now you can come back and edit it all on Revit after the fact because it's all 1427 01:14:14,816 --> 01:14:16,436 native Revit stuff that you can edit. 1428 01:14:17,176 --> 01:14:21,196 But the whole point about taking data, which represents knowledge over 1429 01:14:21,196 --> 01:14:25,036 decades and reusing it in a systematic fashion so that it's much faster 1430 01:14:25,296 --> 01:14:29,396 to, to, to get to resolve design is the main thing about the catalog. 1431 01:14:29,576 --> 01:14:32,756 And, and so, you know, people might ask who are, you know, Revit users? 1432 01:14:33,136 --> 01:14:34,596 Is there a family editor for the catalog? 1433 01:14:35,466 --> 01:14:36,556 Yeah, it's called Revit. 1434 01:14:36,876 --> 01:14:38,756 Whatever you put in Revit you can put into the catalog. 1435 01:14:39,106 --> 01:14:40,716 It's just a matter of that's the way it works. 1436 01:14:40,856 --> 01:14:44,116 So, you know, people that have been using this on projects at some of our 1437 01:14:44,116 --> 01:14:48,716 early firms, they realize, oh, well if I want actually standards of quality 1438 01:14:48,976 --> 01:14:53,636 in my architecture practice around sustainable materials in the projects, 1439 01:14:54,596 --> 01:14:57,516 I can just do that by loading them into the catalogs that people use. 1440 01:14:57,536 --> 01:15:00,916 And then by default it'll be the easiest thing for them to do is just use that. 1441 01:15:01,791 --> 01:15:04,691 And it's the opposite of the garbage and garbage out. 1442 01:15:04,691 --> 01:15:07,331 If I want great stuff coming out the back, I put great stuff into the 1443 01:15:07,331 --> 01:15:09,891 catalog and then great stuff comes out the back on all the projects. 1444 01:15:09,951 --> 01:15:14,371 So, um, firm principles that our technology leaders are thinking about it 1445 01:15:14,371 --> 01:15:19,371 that way is that they have the opportunity to enforce quality and sustainability 1446 01:15:19,521 --> 01:15:23,611 through this catalog mechanism, which is a lever that they haven't had in the past. 1447 01:15:24,511 --> 01:15:27,611 Not only that, it's a lot of, you know, a lot of some of these artifacts 1448 01:15:27,611 --> 01:15:29,811 were done by senior designers who aren't at the firm anymore. 1449 01:15:29,991 --> 01:15:30,211 So 1450 01:15:30,751 --> 01:15:33,251 you can't go ask them how to lay out that surgery suite. 1451 01:15:33,251 --> 01:15:35,771 But here you have 10 of 'em that have been sitting on a file server 1452 01:15:35,771 --> 01:15:41,331 somewhere for 10 years, and now you get to leverage it and, and look at it 1453 01:15:41,351 --> 01:15:45,451 in a new context of design for a new facility and then sit down with our 1454 01:15:45,451 --> 01:15:47,771 architect and say, is this a good layout? 1455 01:15:47,831 --> 01:15:48,571 Is this a bad layout? 1456 01:15:48,631 --> 01:15:49,811 How, how would we do this differently? 1457 01:15:49,871 --> 01:15:52,731 And then you can go back and update it in, in the catalog and then use it on. 1458 01:15:52,761 --> 01:15:57,131 It's a way of systematically improving your future projects by harvesting what 1459 01:15:57,131 --> 01:15:58,851 you have on current and previous projects. 1460 01:15:59,626 --> 01:16:01,606 Evan Troxel: So is that what people shift to? 1461 01:16:01,676 --> 01:16:05,166 There's, there's people who are, like you said, gonna be disrupted in their 1462 01:16:05,166 --> 01:16:11,046 normal two hour or two month long, uh, CD drawing phase or, or, you 1463 01:16:11,046 --> 01:16:12,726 know, end of dd, beginning of cd. 1464 01:16:13,386 --> 01:16:17,726 So if, if that's gone, that that amount of time is gone and the people aren't 1465 01:16:17,726 --> 01:16:23,126 needed to do that because the tool's doing it for you, what are people shifting to? 1466 01:16:23,466 --> 01:16:25,286 Do you, what do you think about that? 1467 01:16:28,686 --> 01:16:32,706 Marty Rozmanith: So most of that acceleration happens in the DD process. 1468 01:16:33,046 --> 01:16:35,866 And in fact, this was recognized by some of the principles that we showed 1469 01:16:35,866 --> 01:16:40,346 this to, um, in, in these charettes where they said, you know, we've done 1470 01:16:40,346 --> 01:16:42,866 this in the past where we've done a block and stack and grasshopper, 1471 01:16:42,906 --> 01:16:45,386 and then we have guys go spend a couple months to model this in Revit. 1472 01:16:45,386 --> 01:16:49,831 What we find out is that . When we get to the end of the two months in Revit, what 1473 01:16:49,831 --> 01:16:54,551 we have in Revit doesn't match what we had in Grasshopper because we, we take those, 1474 01:16:54,551 --> 01:16:58,191 those blocks and we start off with cubes in Revit and we start blocking things in. 1475 01:16:58,331 --> 01:17:00,951 But Revit's, parametric, you know, somebody makes a decision to move a 1476 01:17:00,951 --> 01:17:03,471 wall over and then that propagates and something else moves over. 1477 01:17:03,851 --> 01:17:05,311 And that's just the way Revit is, right? 1478 01:17:05,411 --> 01:17:07,751 It propagates changes to keep things consistent. 1479 01:17:07,811 --> 01:17:10,351 So the construction drawings stay coordinated, but what it does is 1480 01:17:10,741 --> 01:17:15,511 over two months, you have the net effect of all of those changes, which 1481 01:17:15,891 --> 01:17:18,791 in this format represents variance. 1482 01:17:19,291 --> 01:17:22,871 You have what you started off with in concept design, and now you ended up with 1483 01:17:22,871 --> 01:17:24,071 something else in production because. 1484 01:17:24,836 --> 01:17:27,746 Those people working for two months introduced a bunch of variants because 1485 01:17:27,746 --> 01:17:29,546 they have an accumulated set of decisions. 1486 01:17:30,086 --> 01:17:33,386 One of the things about Skema is that it avoids all that because it starts with 1487 01:17:33,386 --> 01:17:37,506 these block and stack and immediately generates the same Revit data out of that. 1488 01:17:37,536 --> 01:17:42,066 They absolutely match all the exiting all of the, you know, sizes of things 1489 01:17:42,066 --> 01:17:45,946 are the same in both the, the cubes in the block and stack rep are the 1490 01:17:45,946 --> 01:17:48,706 same as where the walls are in the Revit model that comes out of it. 1491 01:17:49,046 --> 01:17:50,425 And I should say, by the way, that. 1492 01:17:51,056 --> 01:17:53,916 I'm saying Revit a lot, and we use Revit in a lot of the examples because 1493 01:17:53,925 --> 01:17:58,276 Revit has so much market share, but for us, we're kind of BIM agnostic. 1494 01:17:58,936 --> 01:18:02,436 Um, input to the catalog can come from any BIM system. 1495 01:18:03,256 --> 01:18:07,716 You know, it could come from anything done by Graphisoft or Nemetchek 1496 01:18:07,736 --> 01:18:09,276 or dis even Dassault Sytèmes. 1497 01:18:09,296 --> 01:18:12,716 And on the output side it can go to any BIM system too. 1498 01:18:13,256 --> 01:18:17,956 So while we're saying very Revit specific, and that's where our hearts are, obviously 1499 01:18:17,956 --> 01:18:21,675 having built it and knowing we, we, we have a lot of tribal knowledge about 1500 01:18:21,675 --> 01:18:24,596 Revit, which is why when we do one of these things and we do a presentation, 1501 01:18:24,896 --> 01:18:29,476 uh, after one of these charettes in the office with people, we get just as many 1502 01:18:29,675 --> 01:18:32,476 questions about how the Revit data is structured as how Skema works, right? 1503 01:18:32,476 --> 01:18:36,716 People, people really are, uh, they have, uh, strong convictions about the 1504 01:18:36,716 --> 01:18:38,036 way they should structure Revit data. 1505 01:18:38,056 --> 01:18:40,675 And so usually we have all the right answers to those questions. 1506 01:18:40,736 --> 01:18:40,956 So 1507 01:18:40,981 --> 01:18:41,271 Evan Troxel: Yeah. 1508 01:18:41,411 --> 01:18:42,271 Who better to ask? 1509 01:18:42,581 --> 01:18:42,871 Yeah, 1510 01:18:43,776 --> 01:18:46,276 Marty Rozmanith: Um, but that's not to say that you can't use 1511 01:18:46,276 --> 01:18:47,516 it with some other BIM system. 1512 01:18:47,716 --> 01:18:51,876 I mean, it's absolutely, there's nothing prohibiting anybody from applying it 1513 01:18:52,425 --> 01:18:56,916 with different inputs and outputs, uh, than, than Revit inputs or Revit outputs. 1514 01:18:57,716 --> 01:18:59,776 Evan Troxel: It is gotta make it a great presentation and 1515 01:18:59,976 --> 01:19:01,136 communication tool then, right? 1516 01:19:01,136 --> 01:19:07,266 Because if, if you can kind of dial it back to the blocking and stacking Skema, 1517 01:19:07,806 --> 01:19:13,936 totally assured that it's gonna match up with what Revit is gonna show then. 1518 01:19:14,406 --> 01:19:17,856 Because a lot of clients don't speak Revit, they don't speak plans, they 1519 01:19:17,856 --> 01:19:19,256 don't speak those kinds of things. 1520 01:19:19,316 --> 01:19:25,896 And if you can simplify that and show them in a, in a graphical, experiential 1521 01:19:25,996 --> 01:19:28,816 way, the kinds of things that you're trying to communicate with them. 1522 01:19:28,996 --> 01:19:32,296 But, but again, be assured that it's going to work with what you've gotten 1523 01:19:32,386 --> 01:19:32,736 Revit. 1524 01:19:33,076 --> 01:19:35,576 That's, that's, this is a, a big deal. 1525 01:19:36,861 --> 01:19:40,031 Marty Rozmanith: Yeah, and I, uh, up on our blog. 1526 01:19:40,251 --> 01:19:44,671 The, uh, I have a, a video I did of just taking block and stack output 1527 01:19:44,671 --> 01:19:50,191 from Skema into Veris and Revit and just doing AI generated imagery 1528 01:19:50,381 --> 01:19:55,031 very early on the project just to show a client does this feel right? 1529 01:19:55,491 --> 01:20:01,351 Um, but having the geometry be correct about the way that, you know, where 1530 01:20:01,351 --> 01:20:04,031 the buildings will actually be and how big they'll actually be, and that 1531 01:20:04,031 --> 01:20:07,671 sort of stuff to guide Veris into producing the right size of image. 1532 01:20:08,371 --> 01:20:11,711 Um, and it's still very early days on all that AI image generation stuff. 1533 01:20:11,711 --> 01:20:14,511 I mean, you get into, sometimes you still get into weird scale 1534 01:20:14,511 --> 01:20:17,231 problems that, uh, you know, 1535 01:20:17,691 --> 01:20:20,550 people in, people in AEC tech circles will talk about. 1536 01:20:20,771 --> 01:20:22,550 Um, but I'm sure those things will get solved. 1537 01:20:22,651 --> 01:20:27,071 But yeah, the, the, from the standpoint of just taking the, the 1538 01:20:27,961 --> 01:20:30,311 conceptual data and using that to. 1539 01:20:31,921 --> 01:20:32,861 On its own merits. 1540 01:20:32,861 --> 01:20:33,821 It's absolutely valid. 1541 01:20:34,321 --> 01:20:34,611 Evan Troxel: Yeah. 1542 01:20:34,641 --> 01:20:35,131 Awesome. 1543 01:20:35,721 --> 01:20:38,811 Well, what, what have we missed in this conversation that you wanna make 1544 01:20:38,811 --> 01:20:40,131 sure that the audience hears about? 1545 01:20:40,231 --> 01:20:43,291 Uh, you, you've got a new website, domain name launching. 1546 01:20:43,311 --> 01:20:44,251 You've got, uh, 1547 01:20:44,721 --> 01:20:46,171 Marty Rozmanith: Yeah, it's live as of today. 1548 01:20:46,171 --> 01:20:47,421 Skema.Ai. 1549 01:20:47,651 --> 01:20:47,941 Evan Troxel: Okay. 1550 01:20:47,941 --> 01:20:50,891 And that's Skema.ai. 1551 01:20:51,491 --> 01:20:51,711 Marty Rozmanith: ai. 1552 01:20:51,731 --> 01:20:51,951 Yep. 1553 01:20:52,281 --> 01:20:52,581 Evan Troxel: All right. 1554 01:20:52,601 --> 01:20:54,861 And so people can find out more information there. 1555 01:20:55,361 --> 01:20:59,300 Uh, where else should they be watching for all things Skema as we move forward? 1556 01:21:00,261 --> 01:21:01,821 Marty Rozmanith: I would say mainly, mainly the website. 1557 01:21:01,941 --> 01:21:04,941 I will be, um, speaking next week. 1558 01:21:05,131 --> 01:21:06,541 Well, this will air after that. 1559 01:21:06,800 --> 01:21:08,861 Uh, I'll be speaking at AC Tech in New York. 1560 01:21:09,281 --> 01:21:13,061 Um, and then you can come see us if you're gonna be at Autodesk University. 1561 01:21:13,061 --> 01:21:16,061 We're not exhibiting, but we will be at the show. 1562 01:21:16,241 --> 01:21:16,781 And, um, 1563 01:21:17,574 --> 01:21:18,544 Evan Troxel: Gorilla, gorilla 1564 01:21:18,544 --> 01:21:18,904 Marketing. 1565 01:21:19,645 --> 01:21:20,165 Marty Rozmanith: guerrilla marketing. 1566 01:21:21,079 --> 01:21:22,489 Evan Troxel: Back back to the early Revit days. 1567 01:21:22,559 --> 01:21:23,648 Alright, awesome. 1568 01:21:23,879 --> 01:21:24,929 Well, Marty, thanks so much. 1569 01:21:24,959 --> 01:21:27,049 This has been a, a really fun conversation. 1570 01:21:27,249 --> 01:21:30,209 I love the history part of it and I love where it's going. 1571 01:21:30,429 --> 01:21:33,729 So, uh, looking forward to future updates and I'm sure we'll have to have you back 1572 01:21:33,869 --> 01:21:39,729 to do some catch up once, uh, once we kind of, once you get through this launch 1573 01:21:39,789 --> 01:21:41,049 and, and see where things are going. 1574 01:21:41,616 --> 01:21:42,276 Marty Rozmanith: Thanks so much. 1575 01:21:42,276 --> 01:21:42,936 It was a lot of fun.