00:10 Hello everybody. We will get started 00:12 00:12 just momentarily 00:14 00:14 um as everybody starts fiddling 00:18 00:18 filtering in. Um I hope everybody is 00:22 00:22 safe and at home warm and comfortable. 00:26 00:26 The last 48 hours has been, I'm sure, a 00:29 00:29 bit unusual and trying for many of us. 00:33 00:33 >> I just spent the last 2 hours shoveling 00:35 00:35 and still have much more to go. So, 00:49 00:49 I welcome you to our second digital 00:53 00:53 delivery stakeholder group meeting. 00:56 00:56 Um 00:58 00:58 the first one we had our inaugural 01:01 01:01 meeting was in October. 01:04 01:04 Uh and as many of you know that was also 01:07 01:07 during the timeline that we were going 01:10 01:10 through national uh budget negotiations. 01:13 01:13 And so um us at Federal Highway were not 01:17 01:17 able to participate and attend. Uh we 01:20 01:20 thank Roger and the NIBS staff for uh 01:25 01:25 successfully executing that inaugural 01:27 01:27 meeting and uh at least setting the 01:30 01:30 stage for where we were at um nationally 01:32 01:32 as we start to pick up activities 01:35 01:35 etc. moving forward. 01:48 01:48 We will be using the chat functions um 01:54 01:54 within the zoom meeting to correspond. 01:56 01:56 You can also raise your hand um if 01:59 01:59 you've get want to uh contribute 02:01 02:01 verbally and then we will work to bring 02:03 02:03 you in um through uh the zoom uh audio 02:09 02:09 uh into the dialogue. 02:11 02:11 Um 02:13 02:13 we do have our standard disclaimer uh 02:17 02:17 Roger that you had to advance to. You 02:20 02:20 can go ahead and advance to that. And 02:21 02:21 just basically saying that 02:24 02:24 um you know these are not official uh 02:27 02:27 opinions of the US government or federal 02:30 02:30 highway uh that they are the individuals 02:33 02:33 that are making the statements and that 02:36 02:36 we don't endorse products or 02:37 02:37 manufacturers. And so oftent times if 02:40 02:40 anything has shown in a presentation or 02:42 02:42 named by name, it's just because of uh 02:46 02:46 the essential objection of the 02:47 02:47 presentation, the information being 02:49 02:49 provided and that it doesn't reflect a 02:52 02:52 preference, approval or endorsement. 02:57 02:57 Next slide. Roger. 03:04 03:04 Um so I'm Matt Corgan. I'm with Federal 03:06 03:06 Highway Administration. and I'm in our 03:08 03:08 office of R&D on the infrastructure 03:11 03:11 analysis and construction team. Um the 03:15 03:15 rest of the National Institute for 03:18 03:18 Building Science team uh is also with 03:21 03:21 us, Roger Rackley and Mona. Um they help 03:24 03:24 with a lot of the logistics. They've got 03:26 03:26 our contract support uh for this effort. 03:30 03:30 Um I am still actively looking for a 03:34 03:34 state DOT co-chair to help with um you 03:39 03:39 know managing uh not logistics but just 03:42 03:42 like uh keeping high level um engagement 03:46 03:46 with the community and where the needs 03:48 03:48 are and things like that. Um we hope to 03:51 03:51 fill that here quickly from our 03:53 03:53 membership. 03:54 03:54 Um, and again, thanks to the the NIB 03:57 03:57 staff for helping us uh execute the 04:01 04:01 meetings and uh helping us with managing 04:04 04:04 logistics and day-to-day items. 04:11 04:11 Next slide, Roger. 04:17 04:17 And then we do have uh DD SG membership. 04:21 04:21 Uh that is a broad collection of state 04:24 04:24 DOT members as well as uh some targeted 04:28 04:28 industry associations that you see here. 04:32 04:32 um they represent a lot of levels of 04:34 04:34 maturity across the uh associations and 04:39 04:39 the states with regards to their digital 04:41 04:41 delivery uh journey from those that are 04:44 04:44 uh quite far along to those that are 04:46 04:46 just getting started and everything in 04:48 04:48 between. I would dare say um and our 04:52 04:52 industry representatives uh were 04:54 04:54 assigned by their association 04:58 04:58 uh with regards to their involvement uh 05:01 05:01 within the association at a national 05:03 05:03 level to represent those association and 05:05 05:05 their members uh in official capacity. 05:09 05:09 Um we certainly are very happy to have 05:12 05:12 uh those that have agreed and 05:14 05:14 volunteered to participate as members. 05:16 05:16 Um we know that everybody's very busy 05:19 05:19 and uh this uh uh carving out extra time 05:23 05:23 for another initiative is often quite 05:25 05:25 quite difficult. Um but uh we do have 05:30 05:30 this membership here. You can find that 05:32 05:32 on our website and we will get to that 05:34 05:34 momentarily. We do have some resources 05:36 05:36 that we're going to share and I'm kind 05:39 05:39 of covering going to cover a few of 05:41 05:41 these things briefly um for those of you 05:44 05:44 that might not have been able to 05:45 05:45 participate in our previous meetings 05:47 05:47 just so that we can give everybody kind 05:49 05:49 of a baseline on on where to find things 05:52 05:52 but not spend a lot of time uh like we 05:55 05:55 have done going over the details of each 05:58 05:58 of these items uh like we did earlier uh 06:01 06:01 in previous meetings. Um, I will quickly 06:05 06:05 use this list just to go down through 06:08 06:08 and do a roll call of the membership. 06:11 06:11 Uh, just for roll call purposes for 06:13 06:13 today's meeting, we'll start from the 06:15 06:15 top and work our way down in no order of 06:19 06:19 preference other than alphabetical. Um 06:22 06:22 and uh recognizing that some people do 06:25 06:25 have conflicts and can't uh accommodate 06:28 06:28 uh every single meeting, but um uh 06:31 06:31 Cassidy 06:34 06:34 believe she had a conflict today. 06:38 06:38 And Rick similarly. 06:42 06:42 And there's uh Katie. Katie, you're on 06:45 06:45 right? 06:47 06:47 >> Good to see you. 06:49 06:49 >> Hi Katie. Welcome. Uh Cindy representing 06:54 06:54 ARPA, 07:00 07:00 Will Holmes, Kentucky. 07:02 07:02 >> Good afternoon. 07:04 07:04 >> Will uh Ian with Billings Smart? 07:13 07:13 >> No, no, Ian. Um Carrie, Massachusetts. 07:22 07:22 I hope I hope everybody's safe if 07:25 07:25 they're not able to attend. Uh Jennifer 07:29 07:29 Lloyd, Tennessee do 07:31 07:31 >> I'm here. Hello. 07:34 07:34 >> Hi, Jennifer. Welcome. 07:37 07:37 Uh Kevin with Ashto 07:46 07:46 and Allan Melly. I am here, Matt. 07:50 07:50 >> Hi. Um, welcome. 07:53 07:53 >> I hope you're not digging out too much. 07:56 07:56 >> Oh, no. That's what you have uh kids 07:58 07:58 for. 08:01 08:01 >> Uh Devin with Cow Trans 08:08 08:08 Jonathan 08:10 08:10 Porter. 08:11 08:11 >> Hey, how's it going everybody? 08:13 08:13 >> Hi Jonathan. 08:15 08:15 Charlie Purscell, Iowa. 08:23 08:23 Dan Ranki AC 08:30 08:30 Trisha Stfansky in Minnesota. 08:33 08:33 >> I am here. Hi, Matt. 08:36 08:36 >> Yeah, welcome back. Jacob, Texas. 08:40 08:40 >> Good morning, y'all. I'm here. 08:42 08:42 >> Hi, Jacob. Welcome back. And I have a 08:45 08:45 note that director Wayfrick uh from 08:48 08:48 Michigan will be attending, but he's a 08:50 08:50 few minutes late. So glad he can carve 08:53 08:53 out some time. I'm sure he's dealing 08:55 08:55 with a lot of events in his state as 08:58 08:58 well right now. 09:01 09:01 Um 09:04 09:04 let's see. Roger. I think this is where 09:06 09:06 we had the Zoom poll, correct? We want 09:09 09:09 to know who you are that's joining us 09:11 09:11 today. 09:13 09:13 Um, 09:13 09:13 >> yeah. Oh, um, I u Matt, just to let you 09:17 09:17 know, I've been um chatting with Carrie 09:20 09:20 who is who's trying to join, so she 09:22 09:22 should be here 09:24 09:24 any minute. 09:26 09:26 >> Okay, very good. Um so just uh briefly 09:30 09:30 we like to have an idea of of who's uh 09:34 09:34 attending and 09:36 09:36 how well our outreach uh is making it 09:40 09:40 across the spectrum of digital delivery 09:42 09:42 within the transportation arena. So if 09:46 09:46 you could respond to the poll that would 09:49 09:49 be helpful to us. 10:18 10:18 Yeah, I'm not exactly sure what 10:20 10:20 everyone's view is of this poll, but 10:22 10:22 currently we have 73% 10:24 10:24 uh people participated so far. That's 10:27 10:27 rapidly going up. It would be great if 10:29 10:29 we could get a 100, but you know, pass 10:33 10:33 85 90% that's probably the the goal 10:35 10:35 there. 10:37 10:37 >> Thanks, Reckley. 10:38 10:38 >> Do you see the results? I don't know 10:40 10:40 where the results actually show up. This 10:43 10:43 we're trying to use this Zoom poll for 10:45 10:45 the first time. 10:47 10:47 >> I will take a screenshot of the results 10:49 10:49 just in case it doesn't output it in a 10:51 10:51 correct fashion, but when I end the 10:53 10:53 poll, I imagine it will output something 10:55 10:55 useful. 10:57 10:57 We'll give it another, you know, few 10:59 10:59 seconds and then 11:30 11:30 All right. 11:31 11:31 >> Yeah, we're at 85% and uh I will end the 11:35 11:35 poll. 11:36 11:36 >> Thank you, Ragley. 85%'s pretty good. We 11:41 11:41 have it looks like 140 plus 11:45 11:45 attendees, so that's good. Um, 11:50 11:50 considering 11:53 11:53 what's going on outside, 11:58 11:58 >> are you able to see these results? It 11:60 11:60 says it's sharing. 12:01 12:01 >> I can see them. Yes. 12:02 12:02 >> Oh, very good. 12:04 12:04 >> Yeah, I will drop in. 12:06 12:06 >> Yeah. Thank you. 12:15 12:15 >> Roger. Next slide. 12:18 12:18 Sorry. Uh yeah. um this um 12:25 12:25 >> yeah and just as a reminder uh you know 12:28 12:28 we we established the digital delivery 12:30 12:30 stakeholder group really as a a 12:31 12:31 collaborative initiative um where we 12:34 12:34 want to coordinate and integrate a lot 12:36 12:36 of what's going on nationally um with 12:39 12:39 digital delivery in order to keep the 12:42 12:42 dialogue open and uh for us to 12:45 12:45 understand where everybody's uh state of 12:48 12:48 practice is or state of matur maturity 12:50 12:50 level maturity if you will. Um the 12:52 12:52 baseline has kind of been established 12:55 12:55 with a national uh BIM for 12:58 12:58 infrastructure road map that we have 12:60 13:00 published. Um and we will be revisiting 13:03 13:03 that uh later uh later on and in 13:06 13:06 upcoming meetings. Um but you know we 13:09 13:09 really wanted to make sure that we had a 13:11 13:11 good understanding of all these efforts 13:13 13:13 in a collaborative way so that uh we 13:16 13:16 could make sure that there wasn't a lot 13:17 13:17 of duplication of efforts or to 13:19 13:19 understand where the needs were or any 13:21 13:21 gaps or you know urgent items that that 13:24 13:24 needed to be overcome in order to keep 13:27 13:27 digital delivery moving forward and and 13:30 13:30 successful. And just a reminder that it 13:32 13:32 is very much uh intended to be an open 13:35 13:35 group and open dialogue um across the 13:38 13:38 community. And so uh we'll continue to 13:41 13:41 get information out as quickly as we can 13:43 13:43 through our communication channels and 13:45 13:45 our uh newly um up and posted uh website 13:50 13:50 um as well as other emails and and 13:54 13:54 meetings and make the meetings and the 13:55 13:55 recordings uh available to the public as 13:58 13:58 well. um because we really do want to 14:00 14:00 make sure that everybody's kind of uh 14:02 14:02 getting up to speed or uh helping for us 14:05 14:05 to understand um where the industry is 14:08 14:08 at and where the needs are. 14:12 14:12 Next slide, Roger. 14:16 14:16 Um this was our uh session one. We did 14:19 14:19 break in our our all virtual meeting 14:22 14:22 into three smaller chunks of three hour 14:27 14:27 uh events. So, three three-hour events 14:29 14:29 across three days. The first one was 14:31 14:31 last uh Thursday afternoon. Um this is 14:34 14:34 just the agenda. Uh a quick recap of 14:37 14:37 that agenda. Again, we will we did have 14:40 14:40 that it recording just like this meeting 14:42 14:42 we have recorded. Uh we'll be making 14:44 14:44 those resources and recordings available 14:46 14:46 as well. 14:52 14:52 And then for today, um, we have had to 14:55 14:55 be a bit dynamic because of the weather 14:59 14:59 and people's availability. So, we did 15:01 15:01 have to make some adjustments here on 15:03 15:03 the fly. This is the uh latest and 15:06 15:06 greatest of what we have. Some of the uh 15:09 15:09 items that we had originally anticipated 15:11 15:11 hitting today, we will um be doing at 15:14 15:14 our next uh one on Wednesday uh 15:17 15:17 afternoon. Um but uh nonetheless we 15:21 15:21 still have I think some very good topics 15:24 15:24 to uh discuss and present here about 15:26 15:26 various initiatives that are going on at 15:28 15:28 the national level. We expect that we 15:31 15:31 will hear quite often moving forward 15:34 15:34 from some of the larger 15:37 15:37 relevant projects particularly the 15:39 15:39 transportation plug funds uh that are 15:41 15:41 active. Um the two large active ones 15:44 15:44 being BIM for structures, BIM for 15:47 15:47 bridges and BIM for infrastructure. And 15:50 15:50 then there are others uh that will be 15:52 15:52 coming online. We have a few of those 15:54 15:54 being discussed today uh as well. Um and 15:57 15:57 then we do have our advanced digital 15:60 15:60 construction management systems grant 16:02 16:02 projects uh that are underway. Um, we 16:06 16:06 can't really say too much more about uh 16:09 16:09 the future of ADCMS until we have some 16:14 16:14 additional guidance at the national 16:15 16:15 level about moving forward. But there 16:17 16:17 are projects that have been awarded and 16:19 16:19 have been started and the goal uh for 16:22 16:22 those projects was really to be 16:24 16:24 applicable at a national level where 16:26 16:26 they could uh help not only advance uh 16:29 16:29 and move forward but could be used and 16:32 16:32 leveraged by a lot of different agencies 16:34 16:34 across the country as well. So we're 16:36 16:36 going to tap into those expertise and 16:39 16:39 those efforts uh moving forward with a 16:41 16:41 few of the ADCMS project uh updates. We 16:45 16:45 have a few of those today as well as 16:47 16:47 we'll have more uh in future meetings as 16:49 16:49 well. 16:54 16:54 And then this is our uh revised again 16:58 16:58 gen agenda for the Wednesday afternoon 17:02 17:02 uh time session. Um we will have uh some 17:05 17:05 more updates from the transportation 17:08 17:08 pulled fund uh uh uh studies um and get 17:13 17:13 some idea about how we can help them 17:16 17:16 with their deliverables and their 17:18 17:18 progress and provide them any resources 17:20 17:20 or feedback that they might need. uh and 17:22 17:22 we'll also get an additional ADCMS 17:25 17:25 project up update uh from one of the 17:27 17:27 agencies that um got one of the uh first 17:31 17:31 round of awards for their projects. 17:36 17:36 So again, thanks everybody for being 17:39 17:39 flexible and dynamic 17:41 17:41 uh given everything that's going on 17:43 17:43 nationally. Appreciate that. 17:49 17:49 And uh briefly just some of the 17:51 17:51 activities to date and to mention you 17:54 17:54 know the upcoming uh schedule of efforts 17:57 17:57 we did um you know uh have our inaugural 17:60 17:60 meeting uh in person that was part of 18:03 18:03 IHEA in October. This is our uh second 18:07 18:07 uh set of meetings um that we have 18:09 18:09 scheduled here virtually. Um the next 18:12 18:12 meeting uh will be um uh another hybrid 18:16 18:16 inperson and virtual. All of our 18:18 18:18 meetings will have virtual components um 18:21 18:21 to be able to engage the broad uh 18:24 18:24 perspective of the transportation 18:26 18:26 industry. Um but every other one is 18:29 18:29 going to be virtual only for everybody. 18:31 18:31 But then the ones in between those or 18:33 18:33 every other one in between, we expect to 18:36 18:36 uh try to uh have an in-person grouping 18:40 18:40 uh of the DDSG membership uh as well as 18:45 18:45 potentially piggy back on to another 18:47 18:47 national effort whether it be via IEP or 18:50 18:50 for the one in March, the GIS uh 18:53 18:53 conference held by Ashtto annually uh in 18:56 18:56 order to uh leverage our ability to 18:60 18:60 coordinate and engage engage other parts 19:02 19:02 of the transportation sector with 19:04 19:04 regards to digital delivery um and 19:07 19:07 leverage their venue. Uh if you go to 19:11 19:11 our uh recently developed public website 19:13 19:13 which you do see right there uh listed 19:16 19:16 in the middle of the page is nibs.org 19:19 19:19 solutions federal highway administration 19:21 19:21 digital delivery. You can also just do a 19:23 19:23 quick search online digital delivery 19:26 19:26 stakeholder group hub or DDSG hub if you 19:29 19:29 include the hub as one of the terms. 19:32 19:32 Usually you can get to it pretty 19:33 19:33 quickly. Um I found in my experience uh 19:37 19:37 instead of memorizing the website. Um 19:42 19:42 don't know rackly if potentially you 19:44 19:44 might be able to paste that website into 19:47 19:47 the chat for everybody for convenience. 19:50 19:50 Um but again if you just do a search of 19:54 19:54 DDSG uh hub uh in your webinar browser 19:59 19:59 you should be able to uh find it very 20:01 20:01 quickly and it'll come up. 20:12 20:12 Um the uh third meeting with GIST uh 20:16 20:16 will be the afternoon of the 19th, a 20:18 20:18 half day, and uh the morning of the 20:21 20:21 20th, a half day. Um, we will have 20:25 20:25 additional meetings coming up in 2026 20:27 20:27 that we're coordinating uh with the 20:30 20:30 membership and trying to understand and 20:32 20:32 determine uh where other potential 20:35 20:35 venues might be that we could leverage 20:37 20:37 andor items uh to avoid because um it 20:41 20:41 would be a conflict. Um and we do have 20:44 20:44 uh a mechanism to do that uh through our 20:47 20:47 mural board which we will get to a 20:49 20:49 little bit uh a little bit further on. 20:52 20:52 um as well uh because we're kind of 20:54 20:54 hoping to crowdsource that information 20:56 20:56 or leverage your access to uh what items 21:00 21:00 uh you attend in different meetings at a 21:02 21:02 national level uh that we might need to 21:05 21:05 be aware of for planning purposes. So um 21:09 21:09 we appreciate anybody that can help us 21:11 21:11 crowdsource that information as well. 21:15 21:15 Next slide, Roger. 21:19 21:19 Um, and I I'm not going to dwell on this 21:21 21:21 too much because we've covered this 21:23 21:23 quite in depth in the last couple of 21:25 21:25 meetings, but we we do have a a lot of 21:28 21:28 areas that we're trying to cover. 21:30 21:30 Digital delivery is a very much a broad 21:33 21:33 term. We do have a charter for the group 21:36 21:36 uh that you can find uh at the DDSG hub. 21:40 21:40 there's the direct um uh website link at 21:44 21:44 the bottom um that we can get into the 21:48 21:48 chat uh as well, but if you go to the 21:50 21:50 DDSG hub, you will find that link and 21:53 21:53 resource there as well. It really lays 21:56 21:56 out all of these items uh in detail and 21:59 21:59 and how we plan to operate. We do 22:01 22:01 anticipate this being a long-term effort 22:04 22:04 and initiative in order to again foster 22:07 22:07 that collaboration and promote the 22:09 22:09 knowledge sharing uh uh understand the 22:12 22:12 needs and try to address those to the 22:14 22:14 extent that we can um and optimize our 22:17 22:17 investments in digital delivery uh 22:19 22:19 moving forward. Um, I encourage you to 22:22 22:22 go to the the the DDSG hub and I I 22:25 22:25 digest the resources there, including 22:28 22:28 the charter um for a lot of this 22:31 22:31 information and details uh to understand 22:34 22:34 kind of what our goals are and why we've 22:36 22:36 been uh put together um moving forward. 22:39 22:39 And certainly you can reach out to 22:41 22:41 myself uh and or Roger um and the rest 22:45 22:45 of the NIB staff if you have any 22:46 22:46 questions or if you have any trouble 22:48 22:48 locating any of these resources. and we 22:51 22:51 will make sure that we get that 22:52 22:52 information to you. Um, all of our 22:55 22:55 meetings will be listed uh at the DDSG 22:58 22:58 hub as far as registering uh for those 23:00 23:00 events, both virtual and in person. Uh, 23:04 23:04 so in fact, for the next meeting at GIST 23:07 23:07 in March, there are two different sets 23:09 23:09 of links for registering. If you're just 23:12 23:12 going to be uh virtual, there's one set 23:14 23:14 there and there's another set that if 23:16 23:16 you're going to be attending in person 23:18 23:18 or being, you know, a part of the GIST 23:20 23:20 meeting and and staying uh later and 23:23 23:23 going to participate uh with us on site, 23:25 23:25 there's another separate set of 23:27 23:27 registration links at the DDSG hub. 23:35 23:35 Next, Roger. 23:38 23:38 Yeah. And uh just again the the DDSG hub 23:41 23:41 and the website Roger posted uh in the 23:44 23:44 chat uh for you to access and again if 23:48 23:48 you just uh search DDSGhub um usually it 23:52 23:52 comes up pretty quickly as well. 23:55 23:55 Thanks Arger. We went into some detail 23:58 23:58 at the last uh meeting last week and you 24:01 24:01 know the resources and navigating we we 24:04 24:04 are continuing to work on some of the 24:06 24:06 the smaller subtleties. Sometimes when 24:08 24:08 you press a link it goes to the right 24:10 24:10 area but it doesn't always populate the 24:13 24:13 information and you got to hit a second 24:15 24:15 uh item. But um we're still working on 24:17 24:17 those. But you can get to all the the 24:20 24:20 information um just by you know clicking 24:23 24:23 on the the titles uh in each of the 24:26 24:26 section. Um we do have uh again with our 24:30 24:30 intent to have as open and broad 24:32 24:32 engagement and provide feedback to us. 24:34 24:34 We have set up a mural board um at the 24:38 24:38 website and that will continue to be up. 24:41 24:41 It's not just during the meeting. So, if 24:44 24:44 you have an idea or something pops into 24:46 24:46 your mind after this meeting and you're 24:49 24:49 like, "Oh man, I really should have 24:50 24:50 brought that up during the meeting or, 24:52 24:52 you know, want people to to know of 24:54 24:54 what's going on." Um, you can still go 24:57 24:57 into the mural and and post a sticky 24:59 24:59 note um and help us. We do have some of 25:02 25:02 the you know meeting content populated 25:05 25:05 in there with the agenda so you can 25:07 25:07 provide feedback on specific aspects of 25:10 25:10 the agenda or presentations 25:12 25:12 uh there as well. Um, I will let let's 25:16 25:16 see, Rackley, do you want to step people 25:18 25:18 I guess similar to we did last time 25:20 25:20 through the mural just kind of coming in 25:23 25:23 and following you and uh turning off 25:27 25:27 their um their pointers so it's uh 25:30 25:30 easier for people to navigate and those 25:32 25:32 kind of details and just kind of walk 25:33 25:33 through the the mural site briefly for 25:36 25:36 everybody. 25:37 25:37 >> Yeah, absolutely. 25:40 25:40 Right. So, I've pasted a link into the 25:42 25:42 chat uh that will bring you to our 25:44 25:44 mural. Um like what Matt said, this is 25:46 25:46 our sort of collaborative repository for 25:49 25:49 things that are happening in this 25:50 25:50 meeting and then other things uh in the 25:52 25:52 future. We're hoping to use this to 25:54 25:54 collaborate with each and every one of 25:55 25:55 you uh in a new and interesting way, 25:58 25:58 very visual. Uh as we can see, this is 26:00 26:00 the this section of the mural here is 26:03 26:03 the results of our very first meeting. 26:04 26:04 We have a lot of really nice comments 26:06 26:06 from a lot of different people. Um it 26:09 26:09 was a a great success. Uh it was uh 26:13 26:13 really nice to get, you know, feedback 26:14 26:14 from people in a way like this where uh 26:17 26:17 it's not just in a chat that we have to 26:19 26:19 go dig up later and everything. It's 26:20 26:20 just all here. Um so that's really neat. 26:23 26:23 So for today's meeting, we can see here 26:24 26:24 on our splash page. Um 26:28 26:28 uh we have a copy of our agenda. We have 26:30 26:30 a link to the uh FHWA DDSG website. um 26:34 26:34 this link right here. This will uh 26:37 26:37 subscribe you to updates for the DDSG. 26:40 26:40 Um if you want to click to this, it will 26:41 26:41 bring to a short form that you can fill 26:43 26:43 out. Uh I've already pasted in the 26:45 26:45 results of our attendance poll. 26:47 26:47 Um I will collect any links that may be 26:50 26:50 relative to our presentation today. I 26:53 26:53 will paste them in here so they can be 26:55 26:55 available uh to you uh much later just 26:57 26:57 like I did for our previous meeting. 27:02 27:02 >> Right. So if you 27:03 27:03 >> Yes. 27:03 27:03 >> Yeah. Are you going to cover following 27:05 27:05 and and cursor management? Yeah. 27:09 27:09 >> Right. Right. Right. 27:13 27:13 So I can I will briefly do this. I can 27:18 27:18 summon who's ever here. 27:22 27:22 So important details for this mural. If 27:24 27:24 you haven't already clicked on the link 27:25 27:25 in the chat, uh please do so. You can 27:27 27:27 follow other people uh in this so it's a 27:30 27:30 lot easier to see what somebody's 27:32 27:32 talking about. Uh so details for this uh 27:35 27:35 very important thing in the very bottom 27:37 27:37 of your screen mouse over your logo 27:39 27:39 select it and then deselect broadcast my 27:42 27:42 cursor. Uh with everybody's cursor 27:44 27:44 flying around it gets very difficult to 27:46 27:46 read something or see something because 27:47 27:47 everybody is uh you know their little 27:50 27:50 icon is is fluttering about. So it'd be 27:52 27:52 good to disable that. Uh mine is on just 27:55 27:55 so that I can uh show you where 27:56 27:56 everything is. Uh the major way we will 27:59 27:59 be communicating on this is via sticky 28:01 28:01 note. Uh it's very easy to do. So be 28:03 28:03 careful when you double click it will 28:05 28:05 create a sticky note and you can type 28:06 28:06 whatever you want inside of it, you 28:08 28:08 know. Hello. 28:10 28:10 Oh, we're having people move things. I 28:12 28:12 need to lock all this stuff I meant to 28:15 28:15 do. So 28:19 28:19 lock. 28:21 28:21 Okay. Right. So these sticky notes uh 28:25 28:25 they will be how we communicate via 28:27 28:27 mural uh for all of you. If you want to 28:30 28:30 you can also sign it with your name. 28:32 28:32 It's not necessary. If you uh want to 28:34 28:34 leave an anonymous comment that's also 28:36 28:36 acceptable. Uh we would rather have your 28:38 28:38 collaboration uh than not. So do feel 28:41 28:41 free to uh sign your name you know your 28:44 28:44 first name last name. Uh this very first 28:46 28:46 box here this is for general meeting 28:48 28:48 comments. 28:49 28:49 uh you know positive feedback, 28:51 28:51 constructive feedback, unanswered 28:52 28:52 questions, ideas. Feel free to leave any 28:54 28:54 sort of comment here at all. Um, I would 28:57 28:57 challenge each and every one of you to 28:58 28:58 leave at least one sticky note on this 29:01 29:01 uh board either in this general meeting 29:04 29:04 comments section or down below where we 29:06 29:06 have uh stuff that's going on for like 29:10 29:10 the uh Bridgepool fund stuff we'll be 29:12 29:12 talking about later or ADCMS projects 29:15 29:15 for Washington state uh or Oklahoma. as 29:18 29:18 those presentations are going on, if you 29:19 29:19 have comments, questions or concerns, 29:21 29:21 please, you know, double click here, 29:22 29:22 have a sticky note, you know, type out 29:24 29:24 your thing and you can sign it if you 29:25 29:25 want to or not. Uh, that would be very 29:27 29:27 appreciated. Um, the chat is also fine. 29:30 29:30 If you post a question or an idea or 29:31 29:31 something in chat, I will do my best to 29:33 29:33 grab it and put it in a sticky note on 29:35 29:35 here. Um, but it's much preferable if 29:38 29:38 you all get uh comfortable with mural 29:41 29:41 and using it because this will be a 29:42 29:42 recurring thing. We will keep using this 29:45 29:45 uh throughout our other meetings and 29:46 29:46 other events. Uh so yes, that's that 29:50 29:50 pretty much covers it as far as mural is 29:52 29:52 concerned. Uh thank you very much. 29:56 29:56 >> Rackley, could you repost the link one 29:59 29:59 more time? 30:00 30:00 >> Some people that came in late um didn't 30:04 30:04 have access. And then if you could also 30:07 30:07 cover one more time how to turn off your 30:10 30:10 pointer. 30:12 30:12 Absolutely. So, I will post the link 30:14 30:14 really quick here 30:16 30:16 once again. 30:20 30:20 Right. And turning off the cursor. Um, 30:22 30:22 in the very bottom of your screen on 30:24 30:24 mural is a sort of bar of everybody who 30:26 30:26 is currently viewing this mural. If you 30:28 30:28 mouse over your uh logo, it should be 30:33 30:33 the one on the farthest left. Um, that 30:36 30:36 should be you, I believe. If you mouse 30:38 30:38 over that and then there will be a 30:40 30:40 option broadcast my cursor. If you click 30:42 30:42 on that to deselect it, it will turn 30:44 30:44 your cursor off. 30:50 30:50 >> Thank you. 30:51 30:51 >> So I will release all of you from 30:53 30:53 following me now. 30:55 30:55 >> Yeah, you can also follow follow other 30:58 30:58 people if if there's somebody in there, 31:01 31:01 you know, that you're interested in. Um 31:03 31:03 we do encourage you to provide you know 31:06 31:06 your name and who you are. Certainly you 31:09 31:09 can uh remain anonymous if you choose to 31:12 31:12 but it helps us to kind of understand 31:15 31:15 perspectives and you know where the 31:17 31:17 comments are coming from uh within the 31:19 31:19 industry 31:21 31:21 um if you can provide your your name and 31:24 31:24 contact um 31:27 31:27 as well when you come in. 31:31 31:31 But we're going to continue to use this 31:33 31:33 uh as a mechanism to to gather feedback 31:35 31:35 and information and to help us on 31:38 31:38 identifying you know kind of state state 31:40 31:40 of practice and areas of importance etc. 31:44 31:44 Um and to help us coordinate uh future 31:48 31:48 uh meetings and activities as well as um 31:53 31:53 agenda topics as well. So, 31:56 31:56 >> and I would say don't worry it, the 31:59 31:59 things we put in there are locked. You 32:01 32:01 can't really mess anything up. So, and 32:04 32:04 if you create a note you don't want, you 32:06 32:06 can um delete it just by going on it and 32:10 32:10 hitting delete. And if also if you stop 32:13 32:13 if you do anything like zoom in, zoom 32:16 32:16 out, move, you'll stop following the 32:19 32:19 person you are following. So, if you 32:21 32:21 want to follow them again, you just have 32:22 32:22 to go back and highlight their uh name 32:26 32:26 and then hit follow and then you'll be 32:29 32:29 tagged back up with them. 32:32 32:32 >> Things I learned the hard way. 32:34 32:34 >> Yeah. And and you can like for example 32:37 32:37 with the that screen there with the four 32:39 32:39 quadrants that we're viewing. Um you 32:42 32:42 know, they're also colorcoded. Um so you 32:45 32:45 can change the you know, the color of 32:47 32:47 your sticky to to match up. But if you 32:50 32:50 if you don't do that and it's in the 32:52 32:52 right quadrant, we'll figure it out. Um, 32:54 32:54 but you do have the ability to to change 32:57 32:57 the color of this the sticky um to kind 32:60 32:60 of match the color scheme for those 33:02 33:02 quadrants as well. 33:06 33:06 And if you want to move it, you click on 33:08 33:08 the move. When you when you right click, 33:11 33:11 you get this little menu and that gives 33:13 33:13 you control over your 33:16 33:16 note. 33:18 33:18 Oh, it's somebody has said at least one 33:20 33:20 participant indicates that their IT has 33:23 33:23 blocked access to Mural. Um, 33:25 33:25 unfortunately, that's not something we 33:27 33:27 can deal with. Um, that's something that 33:29 33:29 you'll have to speak to your IT 33:30 33:30 department about. Um, I'm not sure why 33:34 33:34 it would be blocked. It might just be an 33:35 33:35 automatic filtering thing. 33:40 33:40 >> Yeah. Um, and I, you know, we'll try to 33:42 33:42 engage, our intent is to engage through 33:45 33:45 a lot of different mechanisms. So you 33:47 33:47 know particularly during the meeting if 33:50 33:50 you want to continue to use the zoom 33:52 33:52 chat uh and you can always you know 33:56 33:56 reach out to uh myself directly through 33:59 33:59 through email mechanisms as well. 34:09 34:09 So that's uh briefly kind of um where 34:12 34:12 we're at uh with the the stakeholder 34:14 34:14 group activities. Um, we do have our 34:18 34:18 first item uh to get some new 34:21 34:21 information that not many people have 34:23 34:23 heard of yet. And so we're uh happy to 34:26 34:26 have uh Jim from Iowa uh give us an 34:29 34:29 update on some of the new pull fund 34:31 34:31 activities. 34:35 34:35 >> Thank you very much. Uh let me get this 34:37 34:37 set up real quick. Uh share screen. 34:60 34:60 There we go. Can you guys see the 35:01 35:01 presenter screen? 35:03 35:03 >> Yes, we can. 35:05 35:05 >> Here a second. 35:08 35:08 I didn't turn on my camera. I'm not sure 35:10 35:10 how to do that now. Ah, there it is. 35:19 35:19 Perfect. Well, thank you everyone. Um I 35:22 35:22 appreciate the opportunity to be here 35:23 35:23 and speaking to you all. Uh I'm going to 35:25 35:25 cover first of all I'm going to cover 35:27 35:27 some highlights and what we are doing 35:29 35:29 with the BIM for Bridge pool of fund 35:31 35:31 deliverables that were delivered in the 35:32 35:32 first phase and how we plan to use them 35:35 35:35 and some activities going forward. Um, 35:38 35:38 you know, we changed the we requested a 35:40 35:40 change in the agenda a little bit 35:42 35:42 because we really believe in 35:43 35:43 collaboration between the BIM for 35:45 35:45 Bridgepool fund and the BIM for 35:46 35:46 infrastructure and I'm glad digital 35:48 35:48 delivery stakeholder group was willing 35:50 35:50 to accept that. Um, I won't take too 35:52 35:52 long if anyone has any questions. My 35:53 35:53 contact information is there. Uh, you 35:55 35:55 can reach out to me after this or ask 35:57 35:57 questions. Um, since the agenda was 35:60 35:60 rearranged, I said, "Well, I can cover 36:01 36:01 10 minutes and some of our initiatives 36:03 36:03 and some of the new poolled funds and 36:04 36:04 activities that we're looking at 36:06 36:06 completing." 36:08 36:08 Here we go. The first is this IOC 36:11 36:11 validation and software certification 36:13 36:13 program. This is a poolled fund we 36:15 36:15 started or proposed about a year, year 36:17 36:17 and a half ago. We've closed out the 36:19 36:19 solicitation. If states still want to 36:21 36:21 participate, the more the marrier. Um 36:25 36:25 the goal of this you know so we have IFC 36:28 36:28 we've created a 4.3 deliverable it's 36:30 36:30 been piloted by a couple states um we 36:34 36:34 identified based on the first BIM week 36:36 36:36 we had some how do you specify IFC and 36:39 36:39 that's this helps address some of that 36:41 36:41 so it's going to create a cert 36:43 36:43 certification and a validation process 36:45 36:45 so if we have an IFC model how do 36:47 36:47 software vendors view it that's where 36:48 36:48 software certification comes in and then 36:51 36:51 if we're asking a consultant to deliver 36:53 36:53 a IFC model, how do we know it's 36:56 36:56 validated? And that's where the 36:58 36:58 certificates come in. And so between the 37:00 37:00 two of those, you know, that's kind of 37:02 37:02 that deliverable. Uh during the first, 37:04 37:04 you know, during the first meeting, we 37:06 37:06 had talked about um I heard discussions 37:09 37:09 on how do we know stuff is secure and 37:11 37:11 safe. Well, that's part of what this is 37:14 37:14 working on. you know, get creating a 37:15 37:15 certification 37:17 37:17 where you don't have to be online 37:18 37:18 creating a report out of that 37:20 37:20 certification or the file validation and 37:22 37:22 how it's going to be used in the future. 37:24 37:24 Um, one of the key by the end of the day 37:27 37:27 all the participating states and the 37:29 37:29 ones that are looking to participate and 37:30 37:30 there's a few more um we have hard conf 37:33 37:33 commitments from 13 states in the FHWA 37:36 37:36 um there's about five or Whoops. There's 37:39 37:39 about five or six more states that are 37:41 37:41 looking at participating. Uh Minnesota, 37:43 37:43 Montana, Arizona, Florida, Illinois, and 37:45 37:45 North Carolina are still working on 37:46 37:46 getting in that. I think we'll probably 37:48 37:48 end up with about 17 18 states that are 37:50 37:50 participating in this poolled fund. So, 37:53 37:53 the first phase is going to be a 37:54 37:54 discovery phase. Um there's been some 37:56 37:56 changes at BSI and this is really going 37:58 37:58 to identify exactly what we need and how 38:01 38:01 we need it and it's going to align with 38:03 38:03 what we've done in the the BIM pool 38:05 38:05 fund. So that design and construction 38:07 38:07 exchange that we developed in the first 38:08 38:08 phase is how do we ensure that use case 38:11 38:11 and the validation goes with that. Um 38:15 38:15 you know that's kind of the highlight 38:16 38:16 and I guarantee by the end of the day 38:18 38:18 there will be a poll in all the 38:19 38:19 participating states 38:21 38:21 uh outlook emails uh looking to get this 38:25 38:25 kickoff meeting scheduled and get this 38:26 38:26 work going. I think it's a very 38:28 38:28 important effort. The response has been 38:29 38:29 really good and we need to get moving on 38:32 38:32 it. Jim, are you still entertaining 38:37 38:37 additional states to join? 38:38 38:38 >> Absolutely. The more the marrier. 38:41 38:41 Excellent. 38:41 38:41 >> Um, yeah. 38:42 38:42 >> One of the one of the other things I do 38:44 38:44 want to mention on this um 38:47 38:47 is we're going to look at taking the 38:49 38:49 funds that we get from this 38:51 38:51 go to BIM for in the infromain steering 38:55 38:55 committee and see if we can leverage 38:56 38:56 this funds and see if we can get some 38:58 38:58 other countries to participate in this. 38:60 38:60 Um, this is an important effort. I 39:02 39:02 guarantee some other countries will have 39:03 39:03 the same challenges we have with the the 39:06 39:06 4.3 implementation. So I think this is a 39:08 39:08 great opportunity to move the needle, 39:11 39:11 you know, nationally, but also help get 39:12 39:12 some work accomplished at the 39:14 39:14 international level. 39:16 39:16 Um, do you do you know um at least maybe 39:20 39:20 from from your perspective on on your 39:23 39:23 DOT side, like if there's a state 39:26 39:26 um that is listening in here and you 39:29 39:29 know this is the first time they're 39:31 39:31 they're aware of this particular pulled 39:33 39:33 fund and want to inquire about 39:35 39:35 participating, who would they contact 39:37 39:37 within their state in order to kind of 39:40 39:40 move that forward? um they can contact 39:42 39:42 me to start if they need to contact 39:44 39:44 within their state. We can help them out 39:46 39:46 there. Um Kyle Clude has been very 39:49 39:49 helpful in helping get this stand up. He 39:51 39:51 deals with the finances. He's with our 39:53 39:53 research and analytics bureau. He knows 39:55 39:55 all the other research 39:57 39:57 members out there that work for all the 39:59 39:59 other states. So if there's a state 40:00 40:00 that's listening that I haven't 40:02 40:02 solicited from um I have reached out to 40:05 40:05 all the BIM for bridge and BIM for 40:06 40:06 infrastructure poolled fund states and 40:09 40:09 you know so all of them have should have 40:11 40:11 received multiple emails from me mass 40:13 40:13 emails individual emails but like I said 40:16 40:16 you know sometimes that stuff slips 40:18 40:18 through an an inbox now we haven't done 40:20 40:20 a fantastic job reaching out to states 40:23 40:23 who aren't one of the current pulled 40:24 40:24 phone members but yeah if there's an 40:26 40:26 additional one out there please reach 40:27 40:27 out to me um we'll do what we can to to 40:30 40:30 get you through. And that's where these 40:31 40:31 other states are right now. Uh 40:33 40:33 Minnesota, Montana, Arizona, Florida, 40:34 40:34 Illinois, North Carolina. They're not 40:36 40:36 listed up on the top of that list there, 40:38 40:38 but um they're working with their 40:40 40:40 research, getting the finances and all 40:41 40:41 of that, and I expect a good share of 40:43 40:43 them will be participating. 40:46 40:46 >> Very good. Thank you. 40:51 40:51 Uh the next research that's looking at 40:53 40:53 using some of the BIM for bridge 40:54 40:54 deliverables. Um there is a research 40:56 40:56 need statement that's being written 40:58 40:58 right now uh in Cobbs. Oh, one other 41:01 41:01 thing I want to thank Ian Hal for 41:03 41:03 helping get the initial scope for this 41:05 41:05 written up and getting the poolled fund 41:07 41:07 helping me get the pool fund kicked 41:08 41:08 kicked off. He did a tremendous amount 41:10 41:10 of work so he deserves some credit for 41:12 41:12 getting us where we are. Um revise the 41:16 41:16 manual for bridge element inspection. in 41:18 41:18 the MBE ASHTTO publication to provide a 41:20 41:20 national standard for location of 41:22 41:22 element identification of element level 41:24 41:24 defects for digital twins. So, this is 41:28 41:28 currently we're working on getting 41:30 41:30 support through COBS um the TRB I think 41:32 41:32 it's AK-14 41:34 41:34 uh 41:36 41:36 support uh JSAN JC JTCES um Scott Becker 41:40 41:40 and I authored this research need 41:42 41:42 statement currently I we have technology 41:45 41:45 asset management and safety and 41:47 41:47 evaluation endorsement or support we're 41:50 41:50 looking at preservation um hopefully the 41:53 41:53 the Astro Cubs research committee will 41:55 41:55 have this as one of their top five I'll 41:56 41:56 go for NCHRP funding. The goal is to 41:59 41:59 kind of get to a digital twin. Uh if you 42:01 42:01 look at the bottom left image, automated 42:03 42:03 AI assessment of defects. There's a lot 42:05 42:05 of software out software out there that 42:08 42:08 can automatically identify defects and 42:10 42:10 bridge components. And then we have this 42:12 42:12 manual for bridge element inspection 42:14 42:14 that's supposed to feed into our asset 42:15 42:15 management deterioration modeling and 42:17 42:17 all that. Well, how do you take that, 42:20 42:20 you know, unmanned aerial system data 42:22 42:22 and actually tie it back to a model? And 42:24 42:24 that's where we're going to build off 42:25 42:25 the design and construction deliverable 42:27 42:27 or investigate that. You know, you know, 42:29 42:29 the research is going to focus on ISO 42:31 42:31 standards. Um, open source 42:33 42:33 nonproprietary standards, which is key 42:35 42:35 and that really aligns with ASHTO 42:37 42:37 resolution 19 that Tristansky talked 42:39 42:39 about last time. Um, I think it's a huge 42:42 42:42 benefit to the industry to really focus 42:44 42:44 on ISO standards that are 42:45 42:45 nonproprietary, you know, similar to 42:47 42:47 PDFs, IFC, and things that align with 42:49 42:49 that. Um, that's a high level review of 42:51 42:51 this. this is moving through. If someone 42:53 42:53 wants a copy of this and provide input 42:56 42:56 uh or if any states want to endorse it 42:59 42:59 individually that would be great. Um 43:00 43:00 this will lead to better deterior 43:03 43:03 deterioration modeling accuracy. Um 43:06 43:06 having a more structured data format 43:08 43:08 will also lead to benefits of AI use and 43:10 43:10 those type of things. Um it's the 43:13 43:13 original MDI was written quite a few 43:14 43:14 years ago and this should be a good 43:16 43:16 update for it. And I really want to 43:18 43:18 thank Scott Becker for help um getting 43:20 43:20 this written up and working with us and 43:22 43:22 getting this moving through Cobbs. 43:24 43:24 And anyone else who wants to support it. 43:26 43:26 Hopefully we can get Jan and JTCS on 43:28 43:28 board. 43:31 43:31 And any, like I said, any individual 43:32 43:32 state that we can list down for support 43:34 43:34 would be awesome, too. And if there's 43:35 43:35 anyone that would interested in being a 43:37 43:37 panel member, uh feel free to nominate 43:39 43:39 anyone. 43:41 43:41 Our la our another one is courtesy of 43:45 43:45 the FHWA. Uh Lyn Warren did a tremendous 43:47 43:47 amount of work in helping this. Um we 43:49 43:49 had a research need statement that was 43:50 43:50 originally written up. Um I think it was 43:53 43:53 through AED80 43:55 43:55 or AD81 43:57 43:57 subcommittee. Um it's to develop a level 43:59 43:59 of information needed and this will be a 44:01 44:01 guide specification for level of 44:02 44:02 information needed for highway bridges 44:05 44:05 to support project development within 44:06 44:06 the BIM. Um it aligns with ISO 1817 and 44:10 44:10 19650. 44:12 44:12 Um the core components you know ACEC has 44:15 44:15 identified a need that this is needed 44:16 44:16 nationally. Um you know there and to me 44:19 44:19 there really needs to be a national 44:21 44:21 standard uh to have uniform expectations 44:23 44:23 on the level of detail, level of 44:25 44:25 information um level of development, 44:27 44:27 model element breakdown and getting a 44:30 44:30 publication. Now where we're looking at, 44:32 44:32 you know, where this really aligns with 44:33 44:33 BIM for bridge and where we're going is, 44:36 44:36 you know, when we we're working on the 44:38 44:38 IDM, ids's US data dictionaries, we're 44:41 44:41 trying to maintain a oneto one:1 44:43 44:43 relationship. So people understand that 44:45 44:45 and this is just another block on that, 44:47 44:47 the one to one to one:1 relationship 44:49 44:49 that this level of information needed 44:51 44:51 will def align with the workflow 44:53 44:53 exchanges from the BIM for bridge pulled 44:55 44:55 fund and BIM from infrastructure. Um the 44:58 44:58 funding came out of the structure side 44:60 44:60 but yeah so you know we're and we're a 45:02 45:02 little bit ahead on that but Ben for 45:04 45:04 infrared is catching up but you know as 45:06 45:06 we progress this there really needs to 45:07 45:07 be a nationalist standard so uh you know 45:11 45:11 the engineering firms have a standard 45:12 45:12 level to work for and there'll be some 45:15 45:15 additional information that comes on out 45:16 45:16 of this um currently this is aligned to 45:19 45:19 uh be work completed by the ben for 45:20 45:20 bridge pulled fund uh the current 45:22 45:22 contractors 45:24 45:24 if there's any questions on that I'd be 45:26 45:26 you know more to happy to answer some 45:27 45:27 later. And uh you know um I really want 45:30 45:30 to give uh credit to Franchesca Meyer. 45:33 45:33 She's the one that wrote this research 45:35 45:35 need statement and helped get it to 45:36 45:36 where it is. Uh Tonglin Warren and the 45:39 45:39 the FHWA who worked uh on her side to 45:42 45:42 help get us funding to get this 45:43 45:43 completed. Um this work should be 45:46 45:46 starting soon. 45:48 45:48 The last thing I want to mention, and 45:50 45:50 I'll be very brief, is we're looking for 45:52 45:52 a supplemental uh solicitation to the 45:55 45:55 poolled fund for IFC4.3 pilot support. 45:58 45:58 Um 45:60 45:60 we've piloted a couple of these and you 46:04 46:04 know, it's a little challenging right 46:05 46:05 now. Um some of the challenges, you 46:08 46:08 know, was coordinating with software 46:09 46:09 vendors. Um the software, you know, IFC 46:13 46:13 4.3 alignmentbased MVD still needs to 46:16 46:16 get finalized. it's in draft format and 46:18 46:18 things like that. So, this will take 46:20 46:20 funding and it'll support individual 46:22 46:22 states that participate in creating IFC 46:25 46:25 models as part of their deliverables. 46:27 46:27 Um, it'll communicate help communicate 46:29 46:29 with one voice to software vendors and 46:31 46:31 it's just not Bentley, it'll be all the 46:33 46:33 software vendors because as we continue 46:34 46:34 to develop these additional workflow 46:36 46:36 exchanges, whether that be through 46:37 46:37 fabrication, which is our next focus, 46:40 46:40 and that type of work, um, it also help 46:43 46:43 document uh challenges that are met and 46:45 46:45 what's needed. Um it really provides us 46:48 46:48 an opportunity to really fully enforce 46:50 46:50 implementing. Uh this was an item that 46:51 46:51 came out of discussions at BIME and 46:55 46:55 there was about eight states that were 46:57 46:57 interested at the time. We will be 46:59 46:59 sending out a email to all the poolled 47:01 47:01 fund participants. In addition, we will 47:04 47:04 you know there'll be a survey with that 47:05 47:05 looking at what they're interested in 47:07 47:07 doing it and we're going to try to get 47:08 47:08 some dates in there to line up. Um at 47:10 47:10 Iowa we've delivered an IFC model 4.3. 47:13 47:13 Pendot's done a couple including one as 47:15 47:15 a model as a legal document. I'm a 47:16 47:16 little envious they beat us to the IFC 47:18 47:18 model as a legal document, but that's 47:20 47:20 just digital delivery jealousy. I'll get 47:22 47:22 over it. Um 47:26 47:26 yeah, so it's docu and then documenting 47:28 47:28 you know another part of it is 47:29 47:29 documenting the updates that are needed 47:31 47:31 with the IDM IDS in the US data 47:33 47:33 dictionary that we have already 47:34 47:34 developed. Um and I really want to 47:36 47:36 stress you know AR19 uh the Astral 47:38 47:38 resolution that um was a secondary 47:41 47:41 benefit of the first BIM for bridge pool 47:43 47:43 fund really focus on open source 47:45 47:45 nonproprietary data standards you know 47:46 47:46 the indirect outcomes that came out of 47:48 47:48 that first poolled fund including Jstan 47:51 47:51 have been really great accompl 47:53 47:53 accomplishments of the poolled fund and 47:55 47:55 I told you I'd keep this under 10 47:57 47:57 minutes. I think I hit my target. Um, if 47:60 47:60 you guys have any questions, yeah, I'm 48:02 48:02 all ears. If anyone wants copies of any 48:04 48:04 of this information, they can have it. 48:06 48:06 Go for it. My My presentations are 48:09 48:09 always an adventure. This is pretty 48:11 48:11 civil, so I'm sorry. 48:13 48:13 >> Fastpaced adventure, Jim, if I might 48:15 48:15 add. 48:17 48:17 >> Well, I'm trying to keep it high level 48:18 48:18 just so people get the gist of it and 48:20 48:20 then if they want more information, I'm 48:21 48:21 more than happy to follow up or as we 48:23 48:23 get a little further in the research, we 48:25 48:25 can get into the weeds. But I I really 48:27 48:27 want to focus on the audience we have 48:28 48:28 here, which 48:30 48:30 tends to be some higher level people and 48:32 48:32 a lot of them will already understand a 48:34 48:34 lot of this stuff and recognize the 48:36 48:36 funding need. Go ahead guys. Is there 48:39 48:39 any questions or do we want to wait till 48:40 48:40 later? 48:42 48:42 Jim, I'll I'll ask a few questions only 48:45 48:45 because um I I'm I'm one of the ones 48:48 48:48 that usually gets called out for having 48:50 48:50 government speak and all the um 48:53 48:53 acronyms. uh and uh recognizing that we 48:57 48:57 may have some people uh joining us that 48:60 48:60 are maybe just starting their digital 49:02 49:02 delivery journey or trying to get 49:05 49:05 informed and uh so a lot of the acronyms 49:08 49:08 can be a bit much and like I you like 49:10 49:10 you know I'd mentioned the ADCMS the 49:12 49:12 advanced digital construction management 49:14 49:14 uh system program and grants um but 49:17 49:17 maybe for some of the less uh less 49:22 49:22 knowledgeable if you could maybe briefly 49:24 49:24 just state like what IFC is and what IFC 49:28 49:28 4.3 is and like what that kind of status 49:30 49:30 or what it means. 49:33 49:33 >> Yeah. 49:35 49:35 So IFC indust industrial foundation 49:38 49:38 classes are an ISO standard. Um they 49:41 49:41 have full adoption. It's an open source 49:43 49:43 nonproprietary. Think of IFC as the the 49:47 49:47 modeling version of PDFs. You know PDFs 49:50 49:50 is an ISO open non-proprietary standard. 49:53 49:53 um it ensures longevity um when I'm you 49:56 49:56 know that's the information delivery 49:58 49:58 manual the actual publication and that's 49:60 49:60 the IDM but I so there's the ISO 50:03 50:03 standard and where that comes in with 50:04 50:04 BSI BSI helped develop the ISO standard 50:07 50:07 and get the published now BSI takes it a 50:09 50:09 step fur further and creates their model 50:12 50:12 view definitions MVDs um they have an 50:15 50:15 alignment based MVD and that's where 50:16 50:16 infrastructure and BIM for bridge come 50:18 50:18 into it we fit under that alignmentbased 50:21 50:21 MVD now That MVD is still in draft 50:24 50:24 format. You know, as part of the pool 50:26 50:26 fund work, we identified a few 50:27 50:27 challenges that need to be updated. We 50:29 50:29 even coordinate with BSI and BSI has 50:31 50:31 been building smart international. 50:33 50:33 Sorry, using using more acronyms. I 50:36 50:36 remember starting in here and everyone 50:37 50:37 kept throwing uh digital delivery 50:39 50:39 acronyms around. I didn't understand any 50:41 50:41 of them, but now I use them and 50:43 50:43 sometimes I forget what the acronym even 50:45 50:45 stands for. I just know the acronym. 50:47 50:47 But so when we're looking at, you know, 50:49 50:49 that's what IFC is. It's an open source 50:51 50:51 nonproprietary and what it really does 50:53 50:53 is enable owners to take ownership of 50:56 50:56 your data and I don't want to be 50:59 50:59 critical of software vendors but you 51:01 51:01 know we did a model as a legal document 51:03 51:03 back in 2017 and I would be willing to 51:05 51:05 bet if I open that up and the newer 51:08 51:08 version of the authoring platform there 51:11 51:11 would probably be viewing challenges of 51:12 51:12 that whereas you get into IFC that gives 51:16 51:16 you a permanent record and then a 51:17 51:17 background backbone for a digital twin 51:19 51:19 into the future. So it's open source, 51:21 51:21 not proprietary. The owners, bridge 51:23 51:23 owners can own that information then. 51:29 51:29 And then LOI, I kind of covered that 51:31 51:31 level of information needed. It's in the 51:33 51:33 presentation. Um 51:37 51:37 >> and 4.3 is the current standard. 51:41 51:41 >> That is the most current standard of um 51:44 51:44 IFC. They are working on a 4.4 which 51:46 51:46 will include tunnels. Um and then once 51:49 51:49 that is completed, you know, that will 51:51 51:51 be rolled into the MVD with that. Now, 51:54 51:54 like I noted earlier, um there's been 51:56 51:56 some changes changes at uh building 51:59 51:59 smart international new leadership and 52:01 52:01 whatnot. And that's and that's where 52:02 52:02 this discovery phase is going to be very 52:04 52:04 important in this pulled fund and making 52:06 52:06 sure, you know, we're in alignment with 52:08 52:08 everyone and we get exactly what we were 52:11 52:11 expecting to get delivered. 52:14 52:14 >> Yeah. And building smart does have a US 52:17 52:17 chapter. Uh many of of you uh are 52:22 52:22 probably engaged and involved at that 52:24 52:24 level, but for those that aren't, there 52:26 52:26 is a a building smart us uh chapter that 52:29 52:29 feeds into the building smart 52:31 52:31 international um representing US 52:34 52:34 interests and companies 52:36 52:36 um and agencies uh as well. um that we 52:41 52:41 have uh Ian uh as one of our members on 52:44 52:44 digital delivery stakeholder group to 52:46 52:46 make sure that we're having that 52:48 52:48 engagement and discussion and 52:50 52:50 coordination with uh um going smart 52:57 52:57 and as uh Terry has uh indicated in the 52:60 52:60 chat um yes ASHTTO has formally uh 53:04 53:04 endorsed and adopted IFC industry 53:07 53:07 foundation class Um and they've got a 53:11 53:11 statement uh uh 53:14 53:14 stating as as much that's available 53:16 53:16 online but 53:18 53:18 >> and that is the the astral resolution 19 53:20 53:20 that is part of that resolution. 53:23 53:23 >> Yeah, resolution. That was the term I 53:24 53:24 was struggling for. Thanks, Jim. 53:27 53:27 >> Oh, sorry. Didn't mean to interrupt, but 53:29 53:29 I guess I interrupted anyway, so I must 53:31 53:31 have meant it. 53:32 53:32 >> It's all It's all good. It's all good. 53:36 53:36 Um, I don't know if anybody's got any 53:39 53:39 questions specifically on these items or 53:42 53:42 or how they can get more information or 53:44 53:44 get get engaged. Um, and certainly throw 53:48 53:48 something in the chat or raise your 53:49 53:49 hand. And uh, Jim's email is in the chat 53:54 53:54 as well. You can reach out him to him 53:57 53:57 directly for followup. 54:05 54:05 Thank you, Jim, so much for filling in 54:08 54:08 for us as we make some adjustments uh to 54:12 54:12 accommodate 54:14 54:14 um weather and 54:16 54:16 uh other people's schedules. 54:19 54:19 >> No, thank you very much for the 54:21 54:21 opportunity to present. I think some of 54:22 54:22 these initiatives are very good. Um, did 54:25 54:25 you want me to share these slides with 54:27 54:27 you guys later or 54:30 54:30 >> Yeah, if you could just send them send 54:32 54:32 them to myself and Roger and then we'll 54:34 54:34 make sure we we make them available for 54:36 54:36 people to follow up as well. 54:38 54:38 >> Yep. And if 54:39 54:39 >> I do 54:40 54:40 >> Yeah. And if anyone has questions out 54:42 54:42 there, yeah, please email. I will 54:44 54:44 definitely respond. Um, and if there's 54:46 54:46 something else that's needed, yeah, I 54:48 54:48 will help with any way I can. 54:52 54:52 >> Yeah. Thanks, Jim. We we will post them. 54:54 54:54 I did drop slides on the mural, too. And 54:57 54:57 so, if anybody has questions, they can 54:59 54:59 go there and write them um on 55:02 55:02 reflection. 55:05 55:05 Um let's see. I guess we're 55:15 55:15 um I don't know that I need to share my 55:18 55:18 screen necessarily, 55:20 55:20 Matt. We're just ready to move on now to 55:23 55:23 uh 55:24 55:24 >> to Washington State. Um 55:27 55:27 >> so 55:28 55:28 >> we can give the 55:30 55:30 >> I'll I'll go ahead and just just set the 55:32 55:32 stage like I had mentioned. You know, we 55:34 55:34 have our our um ADCMS programming grants 55:39 55:39 and um I dropped some information into 55:44 55:44 the chat for everybody that you can link 55:48 55:48 if you want background information on 55:50 55:50 that. it it that program and the grants 55:52 55:52 are targeted at state agencies, state 55:55 55:55 DOS um but very much meant to move the 55:58 55:58 needle on digital delivery and provide 56:00 56:00 some additional resources 56:03 56:03 uh to help. Um there is certainly an 56:05 56:05 emphasis in developing something that 56:07 56:07 can be nationally applicable and not 56:10 56:10 just uh only applicable for one uh 56:13 56:13 specific state. Um and there's a lot of 56:16 56:16 encouragement of collaboration across 56:20 56:20 jurisdictions having multiple states and 56:22 56:22 and also industry partners in those 56:25 56:25 efforts as part of that program. Uh 56:28 56:28 there have been a couple rounds of 56:31 56:31 grants and awards. Uh we expect more um 56:34 56:34 when we've got more information uh to be 56:37 56:37 able to provide. Uh but we did want to 56:40 56:40 highlight some of the projects that have 56:42 56:42 been uh moved forward, particularly the 56:46 56:46 earlier uh project uh grants that um 56:50 56:50 were from the first round uh of the 56:52 56:52 grant program a couple years ago now um 56:56 56:56 through the IIGJA legislation. and we 56:59 56:59 have Washington State DOT uh uh willing 57:04 57:04 and I'm very happy to hear that uh their 57:07 57:07 efforts moving forward um and hopefully 57:10 57:10 generate some dialogue about what others 57:12 57:12 might be doing in a similar space or how 57:14 57:14 they could uh leverage what Washington 57:17 57:17 DOT is doing uh with their first ADCMS 57:22 57:22 grant. Um, and we've got Jim uh online 57:25 57:25 from Washington State to do that for us. 57:28 57:28 Welcome, Jim. 57:30 57:30 >> Thank you. I assume everybody can see my 57:33 57:33 screen and hear me. All right, 57:35 57:35 >> we can. Thank you. 57:36 57:36 >> All right. 57:37 57:37 >> Yes. 57:38 57:38 >> Okay. So, I'm going to take you on a 57:40 57:40 tour of what we're doing with our ADCMS 57:42 57:42 grant. This is like a, you know, 20,000 57:44 57:44 foot elevation kind of overlook of the 57:47 57:47 whole entire grant. And then, uh, I 57:50 57:50 understand we have a lot of time for 57:51 57:51 questions at the end. So, I will stick 57:54 57:54 at 20,000 and then let the questions 57:56 57:56 dive deeper as we go into the conclusion 57:59 57:59 of the presentation. 58:01 58:01 So, we did receive a grant as um Matthew 58:06 58:06 said uh and we've been working on it for 58:10 58:10 about uh a year and a half now and uh it 58:13 58:13 you know takes a while to kind of get 58:14 58:14 the consultants going. So even though we 58:16 58:16 got our award back in November of 2023, 58:19 58:19 we basically been working off about a 58:20 58:20 year and a half. But so I'm going to 58:22 58:22 kind of take you through the slides and 58:25 58:25 see um of course this is an open time. 58:28 58:28 So if you have any questions, feel free 58:29 58:29 to stop us. So the first um few slides 58:34 58:34 I'm going to present are, you know, kind 58:36 58:36 of I would say nothing new to a lot of 58:38 58:38 us who have been working on the digital 58:39 58:39 delivery effort for a while. But I do 58:42 58:42 understand there's a lot of pre uh 58:44 58:44 people in attendance that this may be 58:45 58:45 sometime some of their first, you know, 58:47 58:47 experience with digital delivery. So 58:50 58:50 here's what Washington state currently 58:52 58:52 does for our delivery process right now. 58:55 58:55 Like we have plan sets that we put 58:57 58:57 together in open roads. We're an open 58:59 58:59 roads state and uh we give we finish 59:03 59:03 that off and we put them into a box and 59:05 59:05 we basically give that off to a 59:07 59:07 contractor contractor and our 59:09 59:09 construction oversight team. They go out 59:11 59:11 and they build the product. And then 59:12 59:12 when they're done, they go and they mark 59:14 59:14 up the PDFs that we created. This is a 59:17 59:17 PDF output right here that we create. We 59:19 59:19 put down in this box. They grab that PDF 59:21 59:21 output and they mark it up with um Adobe 59:24 59:24 or or um one is Blue. We use both those 59:29 59:29 products pretty extensively at your 59:30 59:30 agency. And that gets put into a box as 59:34 59:34 an output of their process. Then we have 59:37 59:37 a a process we have at our state called 59:40 59:40 it's called hats. It stands for highway 59:42 59:42 asset tracking system. It is a database 59:45 59:45 pro program that we built that is unique 59:48 59:48 to our state that basically when 59:50 59:50 maintenance has to go out there and work 59:52 59:52 on a sign they can put that information 59:55 59:55 into that box we call hats and it sits 59:58 59:58 there every time you want to get 59:59 59:59 information from one of those entities 60:01 60:01 to the next. It basically is a manual 60:04 60:04 handoff process and there is no 60:06 60:06 basically bringing all that back to the 60:08 60:08 very beginning to enrich our designs at 60:11 60:11 the beginning. What digital delivery we 60:13 60:13 want to do in our state is accomplish 60:15 60:15 this where you can see at the bottom 60:18 60:18 we've now changed it from three boxes to 60:20 60:20 one box. This is where we want to 60:22 60:22 basically all be looking at the exact 60:24 60:24 same box. We want to be dumping things 60:25 60:25 into the same box. We want to be pulling 60:28 60:28 things out of the same box. And we want 60:30 60:30 automated handoffs as it goes from part 60:33 60:33 to part to part. So there's so this 60:36 60:36 whole life cycle of an asset can be take 60:38 60:38 can be taking place. 60:41 60:41 This is out of the uh the report 60:44 60:44 advancing BIM for infrastructure by FHWA 60:47 60:47 which I believe Matthew mentioned 60:48 60:48 earlier today. And this is a diagram 60:52 60:52 that I have liked because it kind of 60:54 60:54 shows what we want to accomplish. On the 60:58 60:58 outside there are these major points of 61:01 61:01 accessing this diagram which is 61:03 61:03 maintenance and operations, construction 61:05 61:05 and design. And each one of those points 61:08 61:08 does things and that's in the different 61:10 61:10 colors and but you can see all these 61:13 61:13 little tiny circles which are around the 61:15 61:15 right down here. They are touches into 61:18 61:18 what? They are touches into a common 61:21 61:21 data environment down here. So you can 61:23 61:23 see there's all these things times at 61:24 61:24 which this common data environment is 61:26 61:26 touched as it as a product goes through 61:29 61:29 its whole life cycle and that whole 61:32 61:32 process as you carry things around and 61:34 61:34 around and around and around that 61:36 61:36 basically creates what we're calling our 61:39 61:39 agency a life cycle. And this is when we 61:43 61:43 really start looking at assets and 61:45 61:45 consider them important because today in 61:48 61:48 our process is what we do as an agency 61:50 61:50 whenever we're dealing with things. We 61:52 61:52 basically we've honed in what we do at a 61:55 61:55 part at a particular part but then we 61:57 61:57 just basically let it die let it sit 61:59 61:59 there. It's only valuable that one 62:00 62:00 particular entity. 62:03 62:03 At our agency we have I'm going to say 62:06 62:06 four major food groups. Okay. They are 62:09 62:09 uh construction and design which are 62:11 62:11 obvious but we call it in our agency we 62:13 62:13 call it maintenance and traffic which of 62:15 62:15 other agencies would call it operations 62:17 62:17 or maintenance and operations but these 62:20 62:20 are effectively the four main food 62:21 62:21 groups of our agency. Each one part of 62:24 62:24 this of our agency has taken and done 62:27 62:27 things inside their box that has 62:30 62:30 basically perfected the way they do 62:32 62:32 their business and their work. design 62:34 62:34 has perfected the process using open 62:37 62:37 roads on our agency to produce the plan 62:39 62:39 sheets that I showed earlier. 62:41 62:41 Construction has perfected their process 62:43 62:43 to do whatever they need to do to 62:45 62:45 process change orders to pay contractors 62:48 62:48 to set up contracting processes. U they 62:50 62:50 do that great maintenance over there as 62:53 62:53 I mentioned a little bit ago. They use 62:55 62:55 hats. They're good at that. They can 62:57 62:57 they can take care of everything inside 62:59 62:59 that. and our traffic people for 63:02 63:02 specifically traffic signs are are 63:04 63:04 basically our overseers of the whole 63:06 63:06 entire data that we have for signs and 63:09 63:09 all this happens and all of our aside of 63:12 63:12 our agency is working and doing great. 63:14 63:14 They're doing fantastic. WSDOT is a 63:16 63:16 fantastic organization. 63:18 63:18 The problem with this all is we don't 63:21 63:21 connect it. And this is what I my grant 63:25 63:25 is doing. Everything in orange is what 63:29 63:29 my grant is doing. We're wanting to 63:32 63:32 figure out with our agency on one simple 63:35 63:35 asset and that is a traffic sign. How do 63:38 63:38 I do this? How do I bring all these 63:40 63:40 parts and pieces the four main food 63:42 63:42 groups of our agency together to connect 63:45 63:45 them? And you can see I've taken the 63:47 63:47 term common data which comes from the uh 63:52 63:52 FHWA road map. I changed to connected 63:55 63:55 data and this is important that we kind 63:59 63:59 of figured out as we were going through 64:00 64:00 the process because when we started a 64:02 64:02 year and a half ago we were looking for 64:03 64:03 a common data environment but we 64:06 64:06 realized after a course of time is that 64:08 64:08 common is going to be extremely 64:11 64:11 difficult to do. Why? Because each one 64:13 64:13 of these entities going on the outside 64:16 64:16 has already effectively perfected their 64:18 64:18 processes. So if we were to ask cats for 64:22 64:22 example on the right side of that 64:23 64:23 diagram to basically become in the part 64:27 64:27 of the common data environment cats 64:29 64:29 would basically scream foul because 64:31 64:31 they'd have to redevelop their database 64:33 64:33 and devel redevelop all their code 64:35 64:35 associated with it. So what we decided 64:38 64:38 was we were going to work on a connected 64:40 64:40 data environment to kind of connect all 64:42 64:42 these things together. And I'll show you 64:44 64:44 a slide a little bit later on how we 64:45 64:45 kind of envisioned that and came up a 64:47 64:47 little bit more of that. 64:50 64:50 Now, we explored a lot um IFC's 64:54 64:54 and you know a year and a half ago I I 64:57 64:57 knew nothing about IFC's. I've been to a 64:59 64:59 few I he conferences. I basically heard 65:01 65:01 some presentations about IFC's 65:04 65:04 and I really honestly I I I didn't get 65:07 65:07 it. uh in the course of the last year 65:09 65:09 and a half, I've gotten a lot more 65:12 65:12 information and a lot more study time 65:13 65:13 where I can kind of dig into what an IFC 65:16 65:16 is. And and this might be breaking it 65:19 65:19 down to this is again I'm no data 65:22 65:22 programmer and I've mentioned that a 65:23 65:23 million times. I'm a civil engineer by 65:25 65:25 background, by training. Um I'm 65:28 65:28 admittedly a techie civil engineer, but 65:31 65:31 in all aspects I'm not a data 65:33 65:33 programmer. And so uh there is I think a 65:37 65:37 metamorphosis a change in what we do as 65:40 65:40 an as an industry where people who are 65:43 65:43 civil engineers honestly need to become 65:45 65:45 more data savvy. We need to kind of 65:48 65:48 start getting that understanding of how 65:50 65:50 our product is utilized after we 65:53 65:53 complete our designs. And so when I 65:56 65:56 that's where I kind of started 65:57 65:57 approaching IFC's. I started out 65:58 65:58 becoming more data savvy. I started out 66:00 66:00 coming and learning about it and I kind 66:02 66:02 of broke down in my mind I broke down 66:04 66:04 IFC's into two pieces. I broke them down 66:07 66:07 into images and into the data associated 66:10 66:10 with it. At the last I heap uh there was 66:13 66:13 a presentation done by Connecticut and 66:16 66:16 there was u can't remember exactly the 66:19 66:19 name of the lady that gave the 66:20 66:20 presentation. she'll come to me in a 66:21 66:21 minute, but um she's well known in the 66:24 66:24 whole digital delivery side of things, 66:25 66:25 but she quoted in her presentation a 66:27 66:27 term that I really latched on to. And 66:30 66:30 that was 3DI and 2DI. 66:33 66:33 The I stands for intelligent. 66:36 66:36 And that started to click with me 66:38 66:38 because with IFC's, what I saw was 66:41 66:41 images, but we weren't getting the data. 66:45 66:45 we weren't getting the information that 66:47 66:47 we needed to basically en to enrich that 66:50 66:50 whole life cycle of the particular 66:51 66:51 asset. So on the right hand side over 66:54 66:54 here I have effectively this is a an 66:56 66:56 image effectively an IFC image that we 66:58 66:58 kind of did and you can see it looks 67:00 67:00 like a sign that's rectangular. Okay 15 67:04 67:04 in height 24 in wide but guess what it's 67:08 67:08 an R1-3. 67:10 67:10 What's an R1-3 multi-way 67:14 67:14 stop 4-way. And so this information here 67:18 67:18 what we have the R1-3 multi-way stop 67:21 67:21 4-way 15x 24 and then additional 67:25 67:25 information like post height, post 67:27 67:27 height, uh mounting height, the exact 67:30 67:30 location, all that kind of stuff is 67:32 67:32 vital to us. This is the data on the 67:35 67:35 left hand side that we need in order to 67:38 67:38 turn a particular item into a life 67:40 67:40 cycle. The image on the right hand side 67:44 67:44 for us and what we are basically doing 67:46 67:46 is not as important to us as the data. 67:50 67:50 We today for example most of our signs 67:54 67:54 are installed on our contract simply 67:56 67:56 with a cell inside the CAD which is a 67:59 67:59 circle with a line next to it. Okay, 68:01 68:01 that's all you see. And then beyond that 68:04 68:04 that leads you to things in tables and 68:06 68:06 that basically say all this information 68:08 68:08 that's right here. And this t that table 68:10 68:10 information, all that that richness of 68:13 68:13 the data that's behind the image is what 68:16 68:16 is needed for construction to do their 68:18 68:18 process. It's what's needed for 68:20 68:20 maintenance if they ever had to maintain 68:22 68:22 it to replace it because it got hit, 68:24 68:24 damaged or or some other thing, they 68:27 68:27 need to change the post or something 68:29 68:29 like that. That is the richness of the 68:31 68:31 information that we need out of this 68:33 68:33 process. So going back to I got to give 68:36 68:36 Connecticut a lot of of kudos with that 68:40 68:40 term 3DI and 2DI because that to me 68:42 68:42 started to make sense. It started to 68:43 68:43 click a little bit and my work that I 68:46 68:46 did focused more on the eye part of 68:49 68:49 things not on the image. So we actually 68:53 68:53 I know IFC does a lot of image work and 68:57 68:57 we didn't honestly particularly work on 68:59 68:59 that much in my process. We worked 69:01 69:01 mainly on the data side of things. 69:04 69:04 So we looked at what it would take using 69:08 69:08 IFC to import and to export out of open 69:12 69:12 roads open road state as we used um we 69:15 69:15 did I had a consultant doing this work 69:17 69:17 for me they're familiar with Autodesk so 69:18 69:18 they also played with Autodesk a little 69:20 69:20 bit but generically we came up with to 69:24 69:24 take that data that I was showing on the 69:26 69:26 prior screen on the lefth hand side and 69:27 69:27 to extract it out of an IFC model or and 69:32 69:32 to put it through its process 69:34 69:34 uh bring it back to open roads. 69:37 69:37 Basically, it became a ninestep process. 69:40 69:40 It's not as simple as effectively 69:42 69:42 clicking a button to ex ask for the 69:44 69:44 extract and clicking a button to ask for 69:47 69:47 the import. And neither Bentley or 69:50 69:50 Autodesk can do this or they both can do 69:52 69:52 it, but it's not a simple process. And 69:55 69:55 so if we want to succeed, one of my 69:57 69:57 things is if we want to succeed at IFC, 69:60 69:60 then the industry needs to start working 70:02 70:02 on making this a simple extract import 70:04 70:04 for the purpose of the life cycle. And 70:08 70:08 but I don't really in a lot of ways I 70:10 70:10 don't uh actually blame the industry. 70:14 70:14 Here's why. There's those two blocks 70:17 70:17 right there where I put X's on. Those 70:19 70:19 two blocks box have no standard property 70:22 70:22 set for extracting. 70:25 70:25 So that means effectively the Bentley 70:28 70:28 Autodesk of the worlds, the Trimbles, 70:30 70:30 the other entities that want to work in 70:31 70:31 this open platform for the purpose of 70:34 70:34 extracting and exchanging data and all 70:36 70:36 states for example there's nothing that 70:39 70:39 indicates what those two boxes need to 70:41 70:41 look like. So that means that if any one 70:43 70:43 of those vendors or even one of the 70:45 70:45 states wants to build something that 70:47 70:47 takes care of that part, excuse me, it 70:51 70:51 is a custom process. That means 70:54 70:54 everybody's unique and everybody is 70:56 70:56 different. Similarly, on the item types 70:59 70:59 that get exported out of open roads, 71:01 71:01 there's no standard of what item types 71:03 71:03 need to look like. So effectively that 71:04 71:04 means that that is a unique process to 71:07 71:07 every particular state or entity or city 71:09 71:09 or county that wants to be part of this 71:12 71:12 uh process. So I think what we basically 71:16 71:16 come up with is that we need to 71:18 71:18 basically start working towards uh a way 71:22 71:22 to import and export more easily as an 71:25 71:25 industry which means in a lot of ways it 71:28 71:28 means you utilizing common data 71:30 71:30 dictionaries and that's what we did with 71:32 71:32 our work. 71:33 71:33 So, let me show you kind of what um a 71:37 71:37 process is for pulling out a data 71:40 71:40 dictionary uh for let's just say a 71:43 71:43 common term which we all effectively in 71:46 71:46 our infrastructure world we we would use 71:48 71:48 asphalt. Well, the first thing I'd say 71:51 71:51 right off the bat is I don't call 71:53 71:53 asphalt asphalt in the state of 71:55 71:55 Washington. I call it HMA hot mixed 71:58 71:58 asphalt or I think that's what it it's 71:60 71:60 called. Um, you know, that's kind of, 72:03 72:03 you know, neither here nor there. We 72:04 72:04 could probably figure that out. Uh, but 72:07 72:07 I just went into the program into the 72:09 72:09 building smart data dictionary and I 72:11 72:11 just typed in asphalt and I got six uh 72:14 72:14 responses of what asphalt could be out 72:16 72:16 of their searching mechanism and they're 72:18 72:18 right here. And so I started looking at 72:20 72:20 those. I'm like, well, I'm looking for 72:21 72:21 asphalt, asphalt, asphalt that I'd put 72:23 72:23 on a highway or a parking lot. Okay. 72:26 72:26 Well, looking at those, I'd probably 72:27 72:27 discount five of those right off the 72:29 72:29 bat. There's one's called external 72:31 72:31 asphalt layer. I'm like, okay, maybe 72:34 72:34 somebody has indicated that external 72:36 72:36 asphalt layer is what it should be. 72:38 72:38 Okay, so I looked up external clicked on 72:40 72:40 external asphalt layer. Here's what 72:43 72:43 popped up on the left hand side and and 72:45 72:45 one of my, you know, kind of criticisms 72:49 72:49 a little bit is look the definition and 72:50 72:50 the description are blank. I'm like, 72:53 72:53 what does that mean? And I I have no 72:55 72:55 idea. But, you know, being an engineer 72:57 72:57 and having done some work in the piping 72:60 72:60 world, I I look down here under class, 73:02 73:02 it says cast iron pipe, a durable pipe 73:04 73:04 made of cast iron used for plumbing and 73:06 73:06 drainage. Oh, what they mean by external 73:10 73:10 asphalt layer is an external coating, an 73:13 73:13 asphalt coating for a cast iron pipe. 73:16 73:16 Okay. Well, that's definitely not the 73:17 73:17 asphalt that I'm interested in doing for 73:19 73:19 my work. So you know there's things like 73:22 73:22 this and what we are using and what we 73:25 73:25 have for the for my infrastructure um 73:28 73:28 horizontal infrastructure that is just 73:30 73:30 missing inside of the data dictionary 73:32 73:32 side of things is so there's no if I 73:34 73:34 basically want to say to uh any vendor 73:39 73:39 um what I want me to I want a model I 73:42 73:42 want it to be built I want to be able to 73:44 73:44 extract my my information on asphalt it 73:48 73:48 it IFC is not going to be able to help 73:50 73:50 me with that at this moment. 73:53 73:53 So here's effectively how IFC does it 73:56 73:56 and how I did it with traffic signs and 73:59 73:59 this work is available online. Um so 74:03 74:03 what I did is uh my team uh we worked on 74:08 74:08 putting traffic signs into the data 74:11 74:11 dictionary. So into BSTD. So what I did 74:15 74:15 was again I just showed right here I 74:16 74:16 just went to BSDD. I typed in traffic 74:18 74:18 signs and you can see here started 74:21 74:21 listing several things. There's there's 74:22 74:22 more to this, but there was nothing. 74:25 74:25 Discount this first one on the top cuz 74:26 74:26 that's the one that I did. But if you 74:28 74:28 looked at all this other stuff down 74:29 74:29 here, there was information on signing 74:32 74:32 it, but it was probably associated with 74:35 74:35 more buildings than it was with um with 74:39 74:39 road infrastructure. 74:41 74:41 So we came in and we actually um created 74:45 74:45 this thing this one here which is 74:47 74:47 traffic signs and if you clicked on that 74:51 74:51 it would pop up this and it would show 74:53 74:53 you know you've got 42 properties in 74:54 74:54 there and it is associated in IFC 74:57 74:57 properly under the class of sign in IFC. 75:01 75:01 So it is related back into IFC. It's 75:04 75:04 there. Um, and you and it's got 42 75:08 75:08 properties with it and it's got more 75:09 75:09 information associated with it. But let 75:12 75:12 me just click on um, you know, the 75:14 75:14 traffic signs and you can see this 75:16 75:16 fabrication date right here. Pulls up. 75:19 75:19 It's got fabrication date. It's got a 75:21 75:21 description of what a definition of what 75:23 75:23 it is. Simply the date the sign was 75:25 75:25 created, not installed, but created. 75:29 75:29 There is an installation date in there 75:31 75:31 as well. And then you can see down here 75:34 75:34 it's got it's associated with a property 75:37 75:37 in a classes called sign history. And so 75:40 75:40 it's basically if you're a department of 75:42 75:42 transportation and you're looking for 75:44 75:44 something associated with traffic signs, 75:47 75:47 you can see effectively it starts to 75:49 75:49 make sense when you click on this and 75:51 75:51 you bring it in here. And so what we 75:54 75:54 could basically do, and this is another 75:56 75:56 ADCMS grant that I'm involved in, is 75:60 75:60 working with Oregon and California, 76:02 76:02 partnering with them. We're waiting for 76:03 76:03 it to get through its process of of 76:05 76:05 federal funding, but it's been received. 76:07 76:07 But the idea is taking this specific 76:10 76:10 data dictionary associated with traffic 76:13 76:13 signs and and going through with Oregon 76:16 76:16 and California and making it effectively 76:19 76:19 for all three states, maturing this 76:22 76:22 process from what is focused on the 76:24 76:24 state of Washington to what can be 76:26 76:26 utilized in Oregon and California to try 76:28 76:28 to broaden this up to make it something 76:30 76:30 that we can all work on. Now um when you 76:35 76:35 look at this specific traffic sign thing 76:38 76:38 you can see that there's fabrication 76:39 76:39 date but the the value that comes to it 76:41 76:41 from uh the that the vendors get out of 76:44 76:44 it they start getting the exact code for 76:47 76:47 which should be in their program if they 76:50 76:50 want to talk about fabrication date. 76:53 76:53 Okay. So, it's got the richness to it 76:56 76:56 that vendors need to be able to start 76:58 76:58 working on products that can effectively 77:00 77:00 be more uh universal that more entities 77:05 77:05 can start working on. Now, um when we 77:09 77:09 went through our process of creating it, 77:12 77:12 um there's, by the way, there's a QR 77:14 77:14 code right there if you want to scan it 77:16 77:16 with your phone and do some multitasking 77:18 77:18 for a minute. This will take you 77:20 77:20 directly to the BSDDD search for our 77:23 77:23 traffic signs. So, you can pull it up 77:25 77:25 there and you can kind of play with it 77:26 77:26 and look at it. Um, but it took us, 77:30 77:30 honestly, it took us a long time to 77:32 77:32 create this. I'll get into that in my 77:34 77:34 next slide a little bit, but uh, our 77:36 77:36 latest version is 0.5. Um, we've had 42 77:41 77:41 properties in there and there's seven 77:43 77:43 groups of properties and uh, and we 77:46 77:46 utilized for anybody that's done any 77:48 77:48 kind of experimenting with this, we've 77:50 77:50 utilized the Excel spreadsheet template 77:52 77:52 methodology that the BSDD has out there. 77:56 77:56 Uh, so there are uh, vendors that have 77:60 78:00 created things to um to create data 78:05 78:05 dictionaries. we decided to kind of 78:08 78:08 effectively I'm going to go right to the 78:09 78:09 be vendor agnostic. I'm going to go 78:11 78:11 right to the spreadsheet happened or 78:12 78:12 given by BSDD and use that methodology. 78:16 78:16 So I can't really speak to the vendor 78:19 78:19 process that might that they might be 78:20 78:20 able to improve this a little bit and 78:22 78:22 their interaction on how to create. Uh, 78:24 78:24 I did play with one of those a little 78:26 78:26 bit and just basically said, well, I I 78:28 78:28 basically have to spend a lot of time 78:29 78:29 learning how that vendor does their 78:31 78:31 process and I didn't feel that was value 78:34 78:34 be use of my time. So, I just stuck with 78:35 78:35 the spreadsheet methodology. 78:39 78:39 So, um, we basically from our whole work 78:42 78:42 that we did on data dictionaries kind of 78:45 78:45 got some lessons learned popped up here. 78:49 78:49 What I can basically give is I give very 78:51 78:51 good kudos to BSDD and their spreadsheet 78:55 78:55 and their online application. Uh it 78:59 78:59 worked and I know that uh they spent 79:02 79:02 they've had to have spent a lot of time 79:04 79:04 on that spreadsheet. I'm an Excel geek 79:05 79:05 and that was a very impressive Excel 79:08 79:08 spreadsheet that does that work. Uh so 79:11 79:11 kudos to them there. It was fantastic. 79:14 79:14 It worked. Um it did take some there was 79:19 79:19 um I did have I actually got an intern 79:22 79:22 and the intern I got was a data intern 79:25 79:25 and new JSON files and uh Python and as 79:30 79:30 a result was able to create a little 79:32 79:32 application to do some of the work that 79:34 79:34 basically takes the Excel spreadsheet 79:36 79:36 and dumps and creates the um I might be 79:39 79:39 missing this somewhere but I think it 79:40 79:40 creates the JSON file that that can then 79:43 79:43 get uploaded into the BSDDD tool. So he 79:46 79:46 created a little program for me which is 79:47 79:47 perfect for civil engineer because I can 79:49 79:49 look at all the attributes for the signs 79:52 79:52 and get them all right, get them all 79:53 79:53 related correctly. He took care of the 79:55 79:55 Python and took care of that exporting 79:58 79:58 process and JSONs and all that stuff and 80:01 80:01 then got it to where all I have to do is 80:03 80:03 take the output and upload it into BSDD. 80:06 80:06 So I think that that's something that's 80:08 80:08 like a tool for example that BSDD might 80:10 80:10 be able to make available. um you can 80:13 80:13 have what I've done uh and so uh to 80:16 80:16 start with you if you want but that 80:18 80:18 would really help a tool that would 80:20 80:20 basically take that exporting of that 80:22 80:22 spreadsheet and make it easier to for 80:24 80:24 somebody like civil engineering to put 80:26 80:26 into BSDD. 80:28 80:28 Um we didn't have any training out there 80:30 80:30 that we could find. Uh we looked all 80:32 80:32 over the place. Um, the best way we 80:36 80:36 honestly did was we had we uh we did 80:38 80:38 talk to BSI a few times and uh got some 80:41 80:41 few emails back and forth that helped us 80:43 80:43 kind of figure things out. Uh, but we 80:47 80:47 did it the hard way and it took us about 80:49 80:49 40 to 60 hours literally of work to for 80:52 80:52 us to put in that signing traffic sign 80:56 80:56 um into the BSDD. That's that's a long 80:58 80:58 time. time and if you have to expand 80:59 80:59 that out amongst all the assets we need 81:02 81:02 to be considering that is a lot of work. 81:05 81:05 Um, however, I will say this once we 81:09 81:09 most of that 40 to 60 hours was spent 81:11 81:11 figuring how to work the spreadsheet, 81:14 81:14 figuring how to do the export, figuring 81:16 81:16 how to make that process work and learn 81:18 81:18 it. If training were available to do 81:20 81:20 that, that would make that process much 81:23 81:23 shorter. And but I can tell you too that 81:26 81:26 we started playing with a second data 81:29 81:29 dictionary associated with um can't 81:33 81:33 remember what we did but was it 81:34 81:34 guardrail? I think it might have been 81:36 81:36 guardrail. We played around with 81:37 81:37 guardrail and we just decided well oh no 81:40 81:40 it was 88 curb ramps. We played around 81:42 81:42 with 88 curb ramps because let's just 81:43 81:43 see if we can create a data dictionary 81:45 81:45 for 88 cur curb ramps and we started 81:47 81:47 doing it. It was honestly you know a 81:48 81:48 couple hours and we had a pretty decent 81:50 81:50 data dictionary associated for with 88 81:53 81:53 curb ramps. So we didn't take it too 81:54 81:54 far. We just were experimenting on how 81:56 81:56 long it might take to do a second one. 81:58 81:58 So while it's 40 60 hours to do that 82:00 82:00 first one, it's probably going to be 82:02 82:02 probably five hours to do a second one 82:04 82:04 subsequent ones. So much less. The 82:07 82:07 largest thing we had as a problem was 82:11 82:11 getting people to agree on attributes. 82:13 82:13 So I said we had 42 attributes in our 82:15 82:15 data dictionary. It took us months to 82:19 82:19 get through the process of getting 82:21 82:21 different parts of our agency to agree 82:23 82:23 on what goes in or what does not go in 82:26 82:26 to that data dictionary. That is going 82:29 82:29 to be the largest problem any of us have 82:31 82:31 to undertake is and this is a a national 82:34 82:34 effort. I want to make it a national 82:35 82:35 effort. Uh and but when you get on that 82:38 82:38 national stage, it takes a lot of time 82:40 82:40 to get people to agree nationally. When 82:42 82:42 I was young and back in the the late 90s 82:45 82:45 and the early as uh I was on national 82:48 82:48 panels to do pretty much the exact same 82:51 82:51 thing for its 82:53 82:53 my cou cameras couldn't speak to my 82:56 82:56 Pelco cameras and I had to have five 82:59 82:59 different programs running at my traffic 83:01 83:01 management center to operate my variable 83:03 83:03 message signs across the across the 83:05 83:05 region and that was very inefficient. I 83:09 83:09 could not swap out parts. If if I had a 83:11 83:11 new vendor come to me that wanted to 83:13 83:13 sell me another variable message sign, 83:15 83:15 that meant another program. And you 83:17 83:17 know, we developed the NTCIP, National 83:19 83:19 Transportation Protocols for IT. And we 83:23 83:23 made that to where it was 83:25 83:25 interchangeable, plugandplay. That took 83:27 83:27 years. And I was on those panels for 83:30 83:30 things like variable message signs and 83:32 83:32 cameras and weather stations. That took 83:35 83:35 years. It was good hard work that needed 83:39 83:39 to be done and the benefits are now seen 83:42 83:42 tremendously 10 to 15 years later. So 83:46 83:46 I'm seeing that we're going to have to 83:47 83:47 do the exact same thing with our data 83:49 83:49 dictionary work that we take on 83:51 83:51 nationally. It's going to be some tough 83:53 83:53 work at the beginning, but the idea is 83:56 83:56 once we get those things locked down and 83:58 83:58 the vendors don't have to be start 84:00 84:00 basically building in unique things 84:02 84:02 going on and on and on, then it's going 84:04 84:04 to start becoming smooth, seamless, and 84:06 84:06 that's our goal. Somebody said earlier 84:09 84:09 today, it's about think about PDF. Yeah, 84:12 84:12 it kind of is thinking about PDF and is 84:15 84:15 um so that we can all kind of basically 84:17 84:17 take that, pass it on to somebody else 84:20 84:20 that can click on it, open it and view 84:21 84:21 it. I would say that I'd add just like I 84:24 84:24 was talking about earlier, I'd add the I 84:26 84:26 to the end of that, an intelligent PDF, 84:28 84:28 something that's got that data embedded 84:30 84:30 into it so that we can actually pull the 84:32 84:32 data out. We can start making life cycle 84:34 84:34 choices on our products. So, um, a 84:38 84:38 little bit of a quandry I'd have to say 84:40 84:40 with with the whole process is searching 84:44 84:44 through the BSDD dictionary is really 84:47 84:47 honestly a pain. Um, 84:50 84:50 I would I I I know the goal is not to 84:54 84:54 create something new inside the data 84:56 84:56 dictionary. We don't want to do that. 84:59 84:59 Uh, or sorry, we do want to create 85:00 85:00 something new. We don't want to copy 85:02 85:02 what's already there. We want if 85:04 85:04 something's already there, like asphalt 85:06 85:06 for example, asphalt was already there. 85:08 85:08 I'm not going to want to recreate it. I 85:10 85:10 want to use it because it's there. The 85:12 85:12 process of searching for it is difficult 85:14 85:14 inside of BSDD. 85:16 85:16 So, like you saw, I came up with six 85:19 85:19 different things associated with 85:20 85:20 asphalt. Only one of them thought it 85:22 85:22 might be related to what I was wanting 85:24 85:24 to find in there, but it really wasn't 85:26 85:26 at the end. So, the process of doing 85:28 85:28 that searching is is difficult. Um 85:32 85:32 there's a lot of information into in 85:34 85:34 BSDD. It's huge, but a lot of it comes 85:37 85:37 from the horizontal or the vertical 85:38 85:38 infrastructure and so um I'm sure the 85:41 85:41 horizontal infrastructure the pool fund 85:43 85:43 study is going to get more robust on 85:44 85:44 that and so um I think that that's 85:48 85:48 something that can be improved in the 85:49 85:49 process. Um 85:52 85:52 definitions and descriptions are not 85:54 85:54 filled out for a lot of things you click 85:56 85:56 on. So a lot of things all you get is 85:58 85:58 basically the title of the item. I think 86:00 86:00 it should be effectively a standard of 86:02 86:02 the of the of the industry that if 86:04 86:04 you're going to input something into the 86:06 86:06 BSTD, that's great. But it must come 86:08 86:08 with a description because for entities 86:11 86:11 outside trying to utilize what you've 86:14 86:14 developed, it doesn't help if all I see 86:16 86:16 is effectively just a few words. Um, but 86:18 86:18 it's basically a word sometimes for the 86:21 86:21 title. I want to see something more 86:22 86:22 robust that indicates to me whether or 86:25 86:25 not I'm picking the right product. So 86:26 86:26 they don't get effectively. If I'm 86:28 86:28 talking about uh guide rail and you're 86:31 86:31 talking about guardrail, you know, we 86:33 86:33 want to make sure that uh that's okay. 86:35 86:35 You can basically call one guide rail. 86:37 86:37 Another person can call it guardrail. 86:38 86:38 But the definitions down below are going 86:40 86:40 to be what are going to tell us it's the 86:42 86:42 metal thing alongside the road on wood 86:45 86:45 post that stops cars or deflects cars or 86:48 86:48 whatever. We come the with the 86:49 86:49 description, but um what it comes back 86:52 86:52 to, you know, is going to be called 86:54 86:54 guide rail or guardrail. 86:55 86:55 you know, it doesn't really matter in 86:57 86:57 the end because it's a computer program. 86:59 86:59 The computer programs can translate on 87:01 87:01 the back side if necessary. Um, but just 87:04 87:04 we need to think about definitions need 87:06 87:06 to be there and descriptions need to be 87:08 87:08 filled out. 87:11 87:11 So thinking about our whole my whole 87:13 87:13 entire grant again coming back to the 87:15 87:15 higher level I'll talk a little bit 87:18 87:18 about that centerpiece which is the 87:21 87:21 connected data environment 87:24 87:24 and why we had to kind of start thinking 87:27 87:27 about connected versus common. 87:30 87:30 So this here is an image that shows two 87:34 87:34 databases. They're plopped into a 87:37 87:37 program and they're plotted out. The 87:40 87:40 purple dots are a 40-year-old database 87:44 87:44 that we have been utilizing for 87:46 87:46 obviously decades and it is very rich 87:49 87:49 with information. It has when sign is 87:52 87:52 installed, fabricated, MUTCD number. 87:56 87:56 It's got whether it was last time it was 87:58 87:58 maintained, you know, it's got wood 87:60 87:60 post, steel post. It's got tons of 88:02 88:02 information with it. Unfortunately, it 88:06 88:06 is geoloccated using an a linear linear 88:10 88:10 referencing system. What does that mean? 88:12 88:12 That means mile post and state route. 88:17 88:17 So, this right here, state route 522 in 88:19 88:19 our state. Milepost, I don't remember 88:22 88:22 exactly what milepost is. Let's just say 88:23 88:23 for sake of conversation, it's 10. Okay, 88:27 88:27 this is 10 right here. And this is 10.1, 88:29 88:29 10.2, 10.3, 10.4, on and on. So this is 88:34 88:34 how uh all of these things inside of our 88:37 88:37 database are plopped onto a imaginary 88:41 88:41 center line of road. 88:43 88:43 Unfortunately that doesn't really help 88:45 88:45 us much when it comes to start thinking 88:49 88:49 about putting things together from you 88:51 88:51 know multiple databases. The stars that 88:54 88:54 you see in here are from a LAR extract 88:58 88:58 that we did using artificial 88:59 88:59 intelligence. 89:01 89:01 And we found the LAR found these signs 89:04 89:04 in the area, the stars. But the problem 89:08 89:08 with the artificial intelligence work 89:10 89:10 that we did is artificial intelligence 89:13 89:13 isn't able to honestly give us that much 89:15 89:15 information. it. It's really really good 89:18 89:18 at get finding a a blank panel in the 89:21 89:21 world saying I think this is a sign and 89:24 89:24 it's really really good at giving me a 89:26 89:26 gloation because of our it's LAR 89:28 89:28 information with imagery associated with 89:30 89:30 it. So we can use the computer to tell 89:33 89:33 us there's these things in the area but 89:36 89:36 beyond that the computer's accuracy 89:38 89:38 starts to drop off very much like it's 89:41 89:41 can guess at an MUTCD number. It's 89:44 89:44 really good with MUTCD numbers. If it's 89:46 89:46 a physical shape that changes like a 89:48 89:48 stop sign or yield sign, two thumbs up. 89:51 89:51 It does great. Um, beyond that, uh, it, 89:55 89:55 uh, some standardized symbols like do 89:57 89:57 not enter, curve warning, pedestrian 90:00 90:00 crossing, uh, signal ahead symbols. It 90:03 90:03 can start getting some of that and does 90:05 90:05 pretty good. Then then the accuracy 90:07 90:07 starts dripping off a lot from there on. 90:09 90:09 So, what we needed to do was figure out 90:12 90:12 a way to bring these two databases 90:14 90:14 together to connect them because of the 90:16 90:16 value associated with each of those. 90:20 90:20 This particular dot right here, it's 90:24 90:24 actually three dots in the database 90:26 90:26 stacked on top of one another because 90:27 90:27 it's a linear referencing system by 90:29 90:29 tenth of a mile. 90:32 90:32 that is but remember it's comes from our 90:34 90:34 40-year-old database extremely rich in 90:37 90:37 data but has really poor location 90:41 90:41 over here are three signs found by 90:43 90:43 artificial intelligence located by GPS 90:47 90:47 really accurate this is information is 90:50 90:50 data rich location rich but data poor if 90:55 90:55 we can connect these then we can 90:57 90:57 actually start bringing them together 90:59 90:59 and through that connected data 91:00 91:00 environment enrich everything throughout 91:02 91:02 this whole life cycle process. 91:05 91:05 So we did that in some in in a thing 91:08 91:08 called gooids. Now this is something 91:10 91:10 that's getting into real database 91:11 91:11 information but somebody can probably 91:13 91:13 type in what a good actually stands for 91:14 91:14 but it's like graphically unique 91:16 91:16 identifier if I think um but that's 91:19 91:19 complicated number right here that you 91:21 91:21 see here over here and down here. This 91:24 91:24 is a good number. So we basically it's 91:27 91:27 basically unique number that can be 91:30 91:30 identif uh attached to an asset that 91:33 91:33 basically can make it trackable or 91:35 91:35 traceable. Somebody some genius figured 91:38 91:38 out how to do this. But we basically 91:41 91:41 realize that we're going to have to take 91:43 91:43 these gooids in the different databases. 91:45 91:45 TSMS is our 40-year-old database up here 91:48 91:48 rich in information. Down here is our 91:50 91:50 LAR information rich in da in location 91:54 91:54 but lacking effectively and all the 91:56 91:56 other information that can provide but 91:58 91:58 we want to basically connect these 92:00 92:00 through these this good information for 92:03 92:03 which we can which we can do we figured 92:05 92:05 out through our process and how to do 92:08 92:08 that. So that data join 92:11 92:11 um it allowed us to um basically start 92:16 92:16 enriching things 92:18 92:18 to start bringing things together to 92:20 92:20 start thinking about um making 92:24 92:24 information more valuable as it goes 92:27 92:27 through its whole life cycle of the 92:29 92:29 process. 92:30 92:30 The first match that we did was on like 92:32 92:32 a 17-mi test section. We just did a 92:35 92:35 match for a little part of it and the 92:37 92:37 first matching of this takes a heck of a 92:40 92:40 long time. 92:42 92:42 It just was um it's honestly becomes if 92:45 92:45 I were to just do you know for a whole 92:47 92:47 entire 7,000 miles we have of our agency 92:49 92:49 this is going to take too long. So we 92:52 92:52 have to come up we haven't figured this 92:53 92:53 out but we have to come up with a way to 92:55 92:55 effectively try to figure out how to 92:56 92:56 match things faster. 92:59 92:59 Um, I have right now I'm going through 93:01 93:01 the process of this particular area 93:03 93:03 where you're seeing this image is an 93:04 93:04 urban location with lots of signs. 93:08 93:08 Um, I'm thinking it's going to take a 93:09 93:09 heck of a long time to do this urban 93:11 93:11 location. So, what I did is I went back 93:12 93:12 to our vendor that supplied us some of 93:15 93:15 our artificial intelligence work and I 93:17 93:17 gave them another stretch of data and 93:19 93:19 imagery that's in very rural Washington 93:22 93:22 state. And what I'm thinking is that 93:26 93:26 this matching system is going to happen 93:28 93:28 very fast in rural areas where our signs 93:31 93:31 are more spread out. Not so many. And 93:35 93:35 I'm thinking that is going to be 93:36 93:36 probably 75% of our miles of our 93:40 93:40 highways in our state are going to be 93:41 93:41 pretty fast to do this join. It's going 93:43 93:43 to be the 25% for which in urban areas 93:46 93:46 for which it's going to take a long time 93:48 93:48 and be a lot a lot of deep effort. So, 93:51 93:51 um, that's something we're looking on. 93:53 93:53 We're experimenting with now with, um, 93:56 93:56 kind of doing a rural area. See if I can 93:58 93:58 do things faster in that area. 94:01 94:01 When it comes down to construction 94:03 94:03 maintenance, what I basically have 94:05 94:05 determined is as we've gone through this 94:08 94:08 process is we must make it easy for 94:12 94:12 them. If we don't make it easy for them, 94:15 94:15 if we don't make it that say time that 94:18 94:18 allow them to save time, then they're 94:20 94:20 not going to adopt this process. So on 94:23 94:23 the right hand side, we experimented and 94:26 94:26 we created a interface for construction 94:28 94:28 and maintenance to use for just a 94:31 94:31 traffic sign to allow them to use a 94:33 94:33 geoloccated device. It can be an iPhone, 94:36 94:36 it can be an iPad, it can be any kind of 94:38 94:38 tablet can be geoloccated with internet 94:40 94:40 connection. 94:41 94:41 And we allowed them to effectively click 94:43 94:43 on a go to out to an area and then 94:45 94:45 basically pull it up geoloc and they can 94:47 94:47 see where they are and they can see dots 94:49 94:49 in the area which basically are the 94:51 94:51 signs for them to consider for 94:53 94:53 inspection purposes or for maintenance 94:55 94:55 purposes inside the area. It worked 94:58 94:58 pretty slick. Uh it was pretty nice. We 95:01 95:01 have we ran one test with it. Uh, and I 95:04 95:04 understand that Utah actually can do 95:06 95:06 this and um, with some of their 95:09 95:09 projects, which I think because they're 95:10 95:10 more advanced at this than we are, but 95:12 95:12 we just created a test environment to do 95:14 95:14 this in, but this the interface we 95:17 95:17 started to play with here and develop 95:18 95:18 for our work. Uh, we hope to mature as 95:21 95:21 we go throughout our our grant process. 95:23 95:23 We're not done with our work. We have a 95:26 95:26 we want to do a pilot project now to 95:28 95:28 basically try to utilize the processes 95:31 95:31 we developed for a whole life cycle of a 95:32 95:32 traffic sign and take that whole process 95:35 95:35 digital. And we're hoping that we take 95:38 95:38 this little um uh application you see on 95:41 95:41 the right hand side and we mature it 95:43 95:43 even more for the construction process 95:45 95:45 and the maintenance process as we go 95:46 95:46 through our pilot program. But if we 95:49 95:49 don't we bas basically learn very 95:51 95:51 quickly in dealing with construction 95:52 95:52 maintenance. If you don't make it easy 95:53 95:53 for them, if you don't save them time, 95:56 95:56 they're not going to be on board. And if 95:58 95:58 I don't have them on board for that 96:00 96:00 whole entire life cycle, 96:03 96:03 then I'm really going to risk making 96:05 96:05 this process work for the agency. So, 96:08 96:08 this is a huge goal for us. 96:12 96:12 My as a result of the work that we did, 96:15 96:15 we effectively completed phase one of my 96:18 96:18 grant. Phase one of my grant was to try 96:20 96:20 to figure out how we as an agency can 96:21 96:21 turn the life cycle of a sign into a 96:24 96:24 digital process. 96:26 96:26 What we what we basically came up with a 96:29 96:29 conclusion is as our work with our work 96:32 96:32 in phase one 96:34 96:34 is a precise location is vital. It is 96:39 96:39 the way to match things. 96:42 96:42 It is very difficult if you're going to 96:44 96:44 be extracting new information to 96:47 96:47 basically match things inside of 96:50 96:50 databases if you don't have an precise 96:52 96:52 location. 96:54 96:54 Um like for example, if we have our 96:58 96:58 information from our maintenance people, 97:00 97:00 they're collecting things. They 97:03 97:03 oftenimes get things based upon where 97:05 97:05 they are on a mile by mile post on our 97:07 97:07 routes. They sometimes are guessing at 97:10 97:10 that because they can't see a mile post 97:12 97:12 marker or their their odome they ran 97:14 97:14 their odometer you know and they kind of 97:16 97:16 guessed that I'm at mile post 57.5 97:19 97:19 you know but they could have actually 97:21 97:21 been on the wrong side of mile post 57 97:23 97:23 and they could be actually 60 56.5 97:26 97:26 just a common you know honest mistake so 97:30 97:30 the precise location better we can get 97:33 97:33 at that that the better we're going to 97:34 97:34 be have we're going to be for all life 97:37 97:37 cycle cycle work. Um the thing that we 97:40 97:40 also determined really quickly is at our 97:42 97:42 agency especially for science because 97:45 97:45 that's what we delved into. We have a 97:47 97:47 lot of redundant steps in our work. Um 97:50 97:50 people create and put it into 97:52 97:52 information to things like all their 97:54 97:54 codes effectively on their on what the 97:58 97:58 METCD code is. They look it up and 97:60 97:60 that's a maintenance action. The design 98:01 98:01 does the exact same thing when they 98:03 98:03 design and construction might actually, 98:05 98:05 you know, be looking at it for the 98:07 98:07 purpose of whether or not they the sign 98:09 98:09 is what they were told to install. 98:12 98:12 There's a lot of redundant steps in our 98:14 98:14 work. We we need real time data to be 98:17 98:17 available to reduce that redundancy. So 98:21 98:21 instead of the guy looking up in 98:23 98:23 maintenance as he's replacing the sign, 98:25 98:25 looking it up through the the sign 98:27 98:27 fabrication manual what MUTCD number is, 98:30 98:30 you know, he just it just populates 98:32 98:32 because he knows he's got a sign 98:34 98:34 fabricated. He knows it's a stop sign 98:36 98:36 and he knows he needs to put it up. It 98:38 98:38 just can he can basically pull that in 98:40 98:40 automatically from the central database 98:42 98:42 because it's there. So that real time 98:45 98:45 data availability is critical. 98:48 98:48 Um, we basically walked through this 98:51 98:51 whole entire process and we cataloged 98:55 98:55 effectively the whole entire steps of 98:57 98:57 how we do signs from beginning of design 98:59 98:59 all the way through a maintenance action 99:02 99:02 effectively where we're going to be 99:03 99:03 looped back around. And because of all 99:05 99:05 those redundancies that we had in the 99:07 99:07 process and all of that work people do 99:10 99:10 because they're having to create the 99:12 99:12 process for themselves, we basically 99:14 99:14 estimated that just from doing our 99:16 99:16 signing in our state, we could save 99:18 99:18 $361,000 99:20 99:20 annually if we were to go to a digital 99:23 99:23 life cycle model process in a connected 99:26 99:26 data environment. So that to us was a 99:29 99:29 big conclusion that we've already 99:31 99:31 reached and I took that decision to my 99:33 99:33 management earlier in this year to try 99:35 99:35 to get backing for advancing digital 99:37 99:37 delivery in our agency. 99:40 99:40 With the work that we did, we did a lot 99:42 99:42 more than what I just talked about. And 99:44 99:44 so we basically did uh we did traffic 99:47 99:47 signs, but we also did um a lot of LAR 99:51 99:51 extraction. We tried curb ramps. We 99:53 99:53 tried some Meer FDE elements. That's 99:55 99:55 some traffic safety uh information that 99:58 99:58 needs to come along with crash uh for 100:01 100:01 crash locations. We did spend a lot of 100:03 100:03 work trying to extract things out of our 100:05 100:05 LAR and imagery work and and so we spent 100:08 100:08 a lot of our effort doing that at the 100:10 100:10 beginning. Um so we did do more than 100:13 100:13 just traffic signs in our work, but I 100:15 100:15 focused today on our traffic signs uh 100:17 100:17 because that's the one we're wanting to 100:18 100:18 take through the whole entire life cycle 100:20 100:20 of things. 100:22 100:22 With that, there is my contact 100:25 100:25 information. I'd be happy to break down 100:27 100:27 into a conversation if anybody wants to 100:29 100:29 contact me in detail and also am able to 100:33 100:33 take questions today. 100:36 100:36 >> Thank you very much, Jim. Uh there were 100:38 100:38 a few questions in the chat. I'm just 100:40 100:40 going to repeat them that way you can 100:43 100:43 have an opportunity to to respond. So 100:46 100:46 the first one is uh back on your 100:49 100:49 challenges with the building smart data 100:52 100:52 dictionary the BSDD. 100:54 100:54 The question is is there a role for 100:56 100:56 Astro to play in seeking nationwide 100:59 100:59 agreement and submission to BSDD 101:02 101:02 recognizing the time that would be 101:04 101:04 involved? 101:06 101:06 >> Um I think 101:10 101:10 the answer is is yes. 101:14 101:14 I think that and this is um a little bit 101:17 101:17 of a soap box for me. So, and this is 101:19 101:19 this is Jim Mayhew's opinion, okay? Um 101:23 101:23 we definitely need a national standards 101:27 101:27 on data dictionaries. The effort that I 101:29 101:29 have had to do over the course of the 101:31 101:31 last year just to do a data dictionary 101:33 101:33 for my agency for data sign for traffic 101:36 101:36 signs 101:37 101:37 is if I had to do that with 49 other 101:40 101:40 states and not to mention counties and 101:41 101:41 cities that's a waste of time as a as a 101:44 101:44 as an as an industry. 101:47 101:47 We need to recognize that 101:50 101:50 and we basically and who who solves that 101:53 101:53 for us? It's like the Astro Green Book 101:55 101:55 does for design standards, right? it 101:58 101:58 would be the same thing effectively 101:59 101:59 that's needed for our industry with 102:03 102:03 these asset this asset information and 102:07 102:07 so to me the answer is definitely who 102:09 102:09 does that is it ASHTTO uh I think 102:12 102:12 they're probably the best aligned to do 102:14 102:14 it honestly um because of what they have 102:17 102:17 done for our industry throughout my 102:19 102:19 career you know I've seen the evolution 102:21 102:21 of the green books um you know I think 102:24 102:24 that something I think they have the 102:26 102:26 ability to do that with getting the 102:28 102:28 collaboration across the states. And so 102:30 102:30 I think I would probably put Hashtto at 102:32 102:32 the helm for that. And I know that the 102:34 102:34 pool fund study for infrastructure is 102:37 102:37 starting to walk down this path of 102:40 102:40 dealing with a lot of the problems that 102:42 102:42 I've brought up and I and I give them a 102:44 102:44 lot of kudos. Unfortunately, my state is 102:46 102:46 one of those idiot idiosyncrasies. I 102:48 102:48 can't get money for participating in the 102:50 102:50 poolled fund study for infrastructure. 102:51 102:51 Although I'm on we're on two other 102:53 102:53 poolled fund studies, but we'll we'll 102:55 102:55 fight that battle. We're working on it. 102:57 102:57 But I would give I'd give credit to that 102:59 102:59 pool fund study for right now for a lot 103:01 103:01 of the work they're doing. I think 103:03 103:03 they're doing fantastic work. They've 103:04 103:04 got an understanding of these problems, 103:06 103:06 too, by the way. But I think AASHTO 103:08 103:08 needs to have some step up a little bit 103:10 103:10 to start working on some standards. 103:14 103:14 >> Yeah. 103:16 103:16 Roger, you had put a couple comments uh 103:19 103:19 in the chat as well. Did you want to 103:21 103:21 elaborate a little bit before I get to 103:24 103:24 the next question? 103:26 103:26 Yeah, I guess um um I mean I think Jim 103:28 103:28 mentioned it in the way that BIM for 103:30 103:30 infrastructure is working on 103:32 103:32 dictionaries. BIM for Bridge is doing 103:35 103:35 that also focused on bridges and so this 103:38 103:38 is a different domain if you will that 103:41 103:41 they're not covering although there's 103:43 103:43 probably some overlapping things in 103:46 103:46 there that could be leveraged and used. 103:49 103:49 So that's one point when we're 103:52 103:52 developing dictionaries to try to not 103:54 103:54 recreate reuse things that others have 103:57 103:57 done and coordination is a a need. Um, 104:01 104:01 and I mentioned that is something that 104:05 104:05 there's a federal highway project that 104:08 104:08 is involved in exploring a central uh 104:11 104:11 BIM transportation library which could 104:14 104:14 be sort of a a role of way for 104:17 104:17 coordinating these kinds of different 104:19 104:19 dictionaries. Um, and Ashtto could be a 104:23 104:23 great home for it. Federal Highway is 104:25 104:25 not trying to uh own or operate this but 104:28 104:28 facilitate it is the understanding. So 104:32 104:32 maybe you know all these things could 104:34 104:34 come together over time if there's 104:36 104:36 enough interest and maybe we'll talk 104:39 104:39 some more about the CBTL in a future 104:42 104:42 session so people know a little more 104:45 104:45 about it. 104:50 104:50 >> Okay. Very good. 104:54 104:54 All right. The next question, Jim, was 104:58 104:58 certainly kudos on the work that you're 105:00 105:00 doing and uh taking on this task um 105:04 105:04 despite all the challenges. Uh the 105:07 105:07 question is how do you think it can be 105:09 105:09 scaled beyond 105:11 105:11 uh even Washington, Oregon, and 105:13 105:13 California maybe more nationally or or 105:16 105:16 you know even internationally I guess 105:20 105:20 >> how can be scaled? Well, um, 105:24 105:24 let me go let me let me go back just a 105:27 105:27 half second. When I created my traffic 105:29 105:29 signs data dictionary, I reached out to 105:31 105:31 several states where I had contacts. I 105:34 105:34 was able to get information from several 105:36 105:36 states on what they have in their data 105:38 105:38 dictionaries for traffic signs. And I 105:40 105:40 did take that into consideration as I 105:42 105:42 built mine. So uh so I basically tried 105:45 105:45 to take the approach of collaborating 105:49 105:49 bringing all those entities that 105:51 105:51 information from those other entities 105:52 105:52 together to try to create what I 105:54 105:54 created. Okay. So the second part of 105:58 105:58 that question or my response really to 106:00 106:00 their question was is 106:03 106:03 how do we basically build from 106:04 106:04 California Oregon and in Washington out 106:08 106:08 and basically what I would say it's to 106:10 106:10 me it seems maybe I'm underthinking this 106:12 106:12 is it seems simple. I I give the work 106:15 106:15 that we we do Oregon's the lead on that 106:18 106:18 ADCMS grant or and so basically we we go 106:22 106:22 through doing like 15 assets and try to 106:24 106:24 create a data dictionary form and and 106:26 106:26 partner with the pool fund study or give 106:28 106:28 them the pool the pool fund study that 106:30 106:30 information. I'm a because of my 106:32 106:32 background with NTCIP 106:35 106:35 and my history with that I whollyedly 106:40 106:40 believe in open collaboration. what I'm 106:43 106:43 doing here, folks. If you want it, you 106:45 106:45 got it. If you're doing something 106:47 106:47 similar, then give it to me. The the 106:50 106:50 fact that that uh some of us believe I I 106:54 106:54 don't know, it's and I and this is why 106:56 106:56 I'm so big on on IFC's and data 106:59 106:59 dictionaries is we need to be able to as 107:01 107:01 an industry collaborate in the work that 107:04 107:04 we're doing. Is my data dictionary going 107:06 107:06 to be perfect for your state? I would 107:08 107:08 probably say no. I bet I I bet you 107:11 107:11 anything it's probably going to get you 107:12 107:12 90% of the way there. And so if I 107:15 107:15 basically saved you 90% of your work, 107:18 107:18 then that should be something you should 107:19 107:19 latch on to and basically say, "Wow, you 107:22 107:22 saved me 90% of my work. What more two 107:25 107:25 more things do I need to add to it?" 107:27 107:27 Then we can deal with that. We can add 107:29 107:29 those two additional things. And if you 107:31 107:31 go into the data dictionary right now at 107:33 107:33 BSDD, I think I'm actually listed as a 107:35 107:35 contact. If you're there's a way inside 107:37 107:37 of BSDDD that you can actually contact 107:39 107:39 me through that and and request a change 107:42 107:42 to that data dictionary. I think we 107:44 107:44 start doing that kind of stuff. 107:45 107:45 Basically, if you're finding that I 107:48 107:48 didn't have, you know, I don't know 107:51 107:51 um sign tilt. Okay, I don't have sign 107:54 107:54 tilts in my data dictionary, but you 107:56 107:56 find it really important that from your 107:58 107:58 state that sign tilt be there, then 108:01 108:01 okay, let's have a discussion about 108:02 108:02 that. Maybe we take care of it inside 108:04 108:04 the data dictionary. Maybe it's 108:05 108:05 something you take care of individually 108:07 108:07 as your state. Um, so I think that 108:11 108:11 that's the way we need to start 108:13 108:13 definitely need to collaborate in our 108:16 108:16 industry and when we build things 108:18 108:18 consider sharing them. 108:22 108:22 >> Yeah. Excellent. 108:24 108:24 Trisha, I saw you had some comments on 108:26 108:26 what the uh infrastructure pulled fund 108:29 108:29 is on doing on the data dictionary. Do 108:31 108:31 you care to elaborate or provide a 108:34 108:34 little more context verbally? 108:36 108:36 >> Yeah, 108:36 108:36 >> I love Yeah, I I love listening to you. 108:39 108:39 You're involved in so many things that 108:42 108:42 you you always catch me up on things. So 108:44 108:44 >> Oh my goodness. Well, I am. I have about 108:47 108:47 14 things open right now. Um so yeah, I 108:51 108:51 was just asking and I'm seeing a lot of 108:53 108:53 comments in the chat. So two things you 108:55 108:55 guys from me. First of all, you know, I 108:57 108:57 hope that Jstan and this ASHTO task 108:59 108:59 force can really um take the lead and 109:02 109:02 get data standards um adopted and 109:07 109:07 endorsed by ASHTO. So that's what we're 109:09 109:09 doing. Jim, I don't know if you were on 109:10 109:10 yesterday. I presented um on that. So 109:13 109:13 new task force been created to say how 109:16 109:16 can ASHTO endorse modern data standards 109:20 109:20 like the BSDD uh the USDD that they're 109:24 109:24 proposing to do. So that's what you know 109:25 109:25 we're hoping for and I love thank you I 109:28 109:28 was just writing for putting pressure 109:29 109:29 and talking about this more and more 109:31 109:31 because we need more states to say this 109:33 109:33 is important. I know Jacob too there's 109:35 109:35 work being done in Texas several other 109:37 109:37 states. So first of all that's happening 109:39 109:39 and and I look forward to being on those 109:42 109:42 um meetings and then bringing back Matt 109:45 109:45 some of that information as far as what 109:47 109:47 happens with ASHTTO. And secondly, yes, 109:50 109:50 I was just looking to see if anybody was 109:52 109:52 on the BIM for infrastructure pool fund 109:54 109:54 or maybe you're going to have an update 109:56 109:56 at the next digital delivery meeting, 109:57 109:57 but I've asked um and so I'm I was I 110:01 110:01 just put in the chat what I was getting 110:03 110:03 from um this is from Abashek and then 110:05 110:05 Aaron Cen. Those are a couple people 110:08 110:08 working on my Els data dictionary. So I 110:10 110:10 just put in the chat what uh Abbashek 110:13 110:13 had written to me and so he had written 110:15 110:15 specifically because we're looking for 110:17 110:17 as soon as possible you know in 110:19 110:19 Minnesota we would use that that 110:21 110:21 information that data uh just like Jacob 110:24 110:24 is saying and just like you're saying 110:25 110:25 Jim we really need some of this as soon 110:27 110:27 as possible and we have a nice connect 110:30 110:30 grant and I can present on that at some 110:32 110:32 point Matt if you want me to but that's 110:34 110:34 really what we're saying there Jim is 110:36 110:36 that we want the vendors the technology 110:38 110:38 solution providers um Bentley and 110:40 110:40 Trimble specifically in this case to 110:42 110:42 come together and get that data passed, 110:45 110:45 you know, within their systems so we 110:47 110:47 don't have to go through the effort that 110:48 110:48 you're talking about, Jim. Um, so we're 110:50 110:50 working on that in Minnesota and we 110:52 110:52 really want to have these data 110:54 110:54 dictionaries as soon as possible. Um, 110:56 110:56 but so then the second comment which I 110:58 110:58 could put it in the chat too. So the 111:01 111:01 context is important. So like I 111:02 111:02 mentioned they're looking at design to 111:04 111:04 construction data exchange and the 111:06 111:06 construction to asset management asbuilt 111:08 111:08 data exchange. So the context Abashek 111:11 111:11 said is important because a full US data 111:13 111:13 dictionary should also have data from 111:15 111:15 asset management and GIS systems. Um and 111:18 111:18 there is the AG AEGIS poolled fund that 111:22 111:22 developed a data dictionary for 111:24 111:24 geospatial LRS road inventoried system. 111:26 111:26 So there is you know that available. So 111:29 111:29 it would take take a combination of 111:31 111:31 those the aegis 111:34 111:34 data dictionaries what's happening with 111:35 111:35 the bridge poolled fund as well as then 111:37 111:37 creating this BIM for infrastructure um 111:40 111:40 data dictionary. So lots of work but I 111:42 111:42 think also what I'm reading here is that 111:44 111:44 they need to have more funding. So 111:47 111:47 looking for more funding um you know in 111:49 111:49 a longer term and so I don't I don't 111:51 111:51 know I don't see any say slated to be 111:54 111:54 ready by July 111:57 111:57 2026. So there is some I think again if 112:00 112:00 anybody else I'm not on the BIM for 112:02 112:02 pulled fund infrastructure um but I just 112:05 112:05 am reading exactly what was sent to me 112:07 112:07 by Abashek so if anyone else has any 112:10 112:10 comments so sorry a lot to say there but 112:12 112:12 again great work Jim signing is a good 112:15 112:15 focus area you guys because signing has 112:17 112:17 a ton of attribution and a ton of signs 112:21 112:21 that are replaced every year and so I 112:24 112:24 think that's a that's a really great 112:25 112:25 topic that you focused on Anything else, 112:28 112:28 Matt, that you wanted to hear from me? 112:31 112:31 >> No, that was perfect. Thank you, Trisha. 112:33 112:33 I think there's an opportunity here 112:35 112:35 obviously with those that are members of 112:37 112:37 the DDSG and just in involved in the, 112:41 112:41 you know, the discussion for us to 112:42 112:42 connect some dots and get the work uh 112:45 112:45 that Jim's been doing over to the uh 112:48 112:48 transportation pulled fund um and you 112:51 112:51 know, back and forth, etc. Um uh let's 112:56 112:56 see. I got a few hands up, so we'll 112:59 112:59 we'll go to hands and then I'll come 113:01 113:01 back to the chat. I Brad, go ahead. 113:05 113:05 >> Yeah, I I really apologize. I missed the 113:07 113:07 meeting the other day. Um uh Trisha, I 113:11 113:11 think it'd be great if you and I talked 113:13 113:13 a little bit about the J stand. Just 113:15 113:15 letting you know that the ASHTO task 113:16 113:16 force, I'm doing a kickoff meeting with 113:19 113:19 Kevin Marsha on Thursday morning. So, we 113:22 113:22 will start that ball rolling. Um, but I 113:24 113:24 think it would be good if I 113:26 113:26 uh get um engaged with with the Jstand 113:30 113:30 folks as well as the other uh electronic 113:33 113:33 engineering standards folks. But just 113:35 113:35 wanted to let you know where that was. 113:37 113:37 >> Yeah, very good. Thank you, Brad. Brad's 113:39 113:39 going to be a a good contact for us as a 113:42 113:42 member with a lot of these activities as 113:44 113:44 well. Glad you're able to get on. 113:48 113:48 >> Yeah. And just remember, I'm not the 113:49 113:49 technical expert here. I know enough 113:51 113:51 about it to be dangerous. Um, but 113:54 113:54 certainly willing to to kind of be that 113:56 113:56 lay on for this group to Ashto and to 113:59 113:59 other leadership uh forums. 114:02 114:02 >> Yeah. No, we we very much appreciate 114:04 114:04 that perspective and and your role with 114:07 114:07 your agency. I hope uh hope the 114:09 114:09 weather's treating you okay. 114:12 114:12 >> I love the winter and I love the snow, 114:13 114:13 so it's all good. 114:16 114:16 >> Um, and then uh Jim, Iowa, go ahead. Now 114:20 114:20 I will speak briefly and I'm just going 114:21 114:21 to piggyback a little bit off what 114:23 114:23 Trisha said. Um you know I think Jstand 114:26 114:26 does have a role in these national data 114:28 114:28 standards. You know the BIM for Bridge 114:30 114:30 Pool Fund has already created a US data 114:33 114:33 dictionary for bridge items but having 114:35 114:35 those national standards and any 114:37 114:37 national standard that comes out in 114:38 114:38 addition you know I know BSI is working 114:40 114:40 with the open geospatial and national 114:42 114:42 standards in that way needs to have a 114:45 114:45 national an ASHTO endorsement in my 114:47 114:47 opinion. That's my opinion, not 114:48 114:48 Ashtto's, but you know there having 114:52 114:52 national standards is what really is 114:54 114:54 going to enable digital delivery. So you 114:56 114:56 don't have 50 states doing 50 different 114:58 114:58 things. Um in my opinion that would be a 115:01 115:01 failure and I think bridge has done a 115:03 115:03 very good job at creating national 115:05 115:05 standards historically and hopefully we 115:08 115:08 continue to do that. I did see one 115:10 115:10 comment in there about um continuing BIM 115:12 115:12 for infrastructure after 2028. Um, I 115:15 115:15 believe the pool fund will have an 115:17 115:17 opportunity to have a phase two when it 115:19 115:19 gets closer to closing out and be 115:21 115:21 determined then that, you know, Iowa can 115:24 115:24 still continue that. Um, if another 115:25 115:25 state wants to lead, well, that's a 115:27 115:27 discussion at a future time. Uh, you 115:30 115:30 know, we don't need to be BIM heroes. 115:31 115:31 Everyone wants to accomplish the same 115:33 115:33 goal. So, thanks. That's all I got. 115:36 115:36 >> Yeah. And in the chat, Jacob from Text, 115:41 115:41 he's one of our um group members as 115:44 115:44 well. He just stating that Texas is very 115:47 115:47 interested. They're working in this area 115:49 115:49 as well and happy to collaborate with 115:51 115:51 you uh Jim and what you're doing in 115:53 115:53 Washington. Um so we'll connect you with 115:57 115:57 Jacob uh and Jacob unless you want to 115:59 115:59 come in and um 116:02 116:02 >> I I just 116:03 116:03 >> elaborate 116:04 116:04 >> chat. I just direct messaged him. So 116:06 116:06 okay information had it. 116:10 116:10 >> Yeah. Excellent. Um, a question. Is 116:13 116:13 there another lead organization that is 116:15 116:15 taking over for Iowa in 2028 to continue 116:18 116:18 the BIM for infrastructure pulled fund? 116:21 116:21 Well, that's not not a question for you, 116:23 116:23 Jim. That's a that's an Iowa question. 116:26 116:26 So, uh, I don't know if they want. 116:28 116:28 >> That's the one I was talking about when 116:30 116:30 I all I've already address. 116:33 116:33 >> I'm catching up. Gotcha. 116:34 116:34 >> 2028 is two years away. In a year or so, 116:37 116:37 they can discuss that. Usually, it's not 116:39 116:39 uncommon to have a one-year extension to 116:41 116:41 a TPF pool fund and that can continue 116:44 116:44 moving forward and then you are allowed 116:46 116:46 to you do one continuing 116:49 116:49 um phase of phase two. Now, BIM for 116:51 116:51 Bridge when it expires, we'll have to go 116:54 116:54 out for solicitation or figure out what 116:56 116:56 our next steps are and helping to 116:57 116:57 complete some of those workflow 116:58 116:58 exchanges in that environment. And I do 117:01 117:01 have a few ideas on that, but we're a 117:03 117:03 little premature to start worrying about 117:05 117:05 that. 117:07 117:07 Thanks. 117:09 117:09 >> Yep. 117:13 117:13 I'm trying to keep up with the chat as 117:15 117:15 it's moving and other chats are coming 117:17 117:17 in. Let me see. 117:25 117:25 Uh there is a I don't know if this is a 117:28 117:28 question for you Jim or not. Um, does 117:31 117:31 anyone think that one of the problems is 117:33 117:33 this is considered an IT data computer 117:35 117:35 issue rather than an engineering one? It 117:39 117:39 seems that most of this information 117:41 117:41 needs to be in the green book or the 117:43 117:43 bridge standards or METCD, etc. Is that 117:47 117:47 a thought? 117:48 117:48 >> I I could speak to that a little bit. 117:50 117:50 >> Yeah. Okay. Um 117:53 117:53 there has to be a marriage between 117:57 117:57 traditional civil engineering practices 117:59 117:59 and technology modern technology. I've 118:03 118:03 mentioned this to my my official title 118:06 118:06 is assistant state design engineer at 118:08 118:08 the agency. So I'm you know sit over the 118:12 118:12 good portion of the state when it comes 118:14 118:14 to uh designing projects. 118:18 118:18 when I first started in you know there I 118:21 118:21 sat down at a computer in 1991 my first 118:24 118:24 job at the agency and did 118:26 118:26 three-dimensional 118:28 118:28 models in for my project back then that 118:31 118:31 was 30 plus years ago okay 118:35 118:35 there needs to be since then effectively 118:39 118:39 the team that we used to create our 118:41 118:41 designs was usually is one squad leader 118:44 118:44 and two lead two entry level not lead 118:46 118:46 but two working level engineers and then 118:48 118:48 underneath them is two technicians. 118:51 118:51 Those are all engineering side staff. 118:54 118:54 The technicians that are underneath 118:55 118:55 there are only the ones that basically 118:57 118:57 do the CAD work and do computations and 118:59 118:59 estimating you know calculations for 119:01 119:01 estimates. What I tell my people 119:04 119:04 that team needs to change. 119:08 119:08 There's two reasons it needs to change. 119:10 119:10 One is because I'm not getting the civil 119:12 119:12 engineers that are coming to me like 119:15 119:15 they used to. I have a lot of vacancies 119:18 119:18 in my civil engineer positions coming 119:20 119:20 out of school. They're not getting to 119:23 119:23 me. 119:25 119:25 So, I don't have the people. Number two 119:27 119:27 is our a whole industry is evolving. 119:31 119:31 Technology is coming more and more and 119:33 119:33 more every day into everything that we 119:34 119:34 do. 119:36 119:36 That means that what I look at that five 119:37 119:37 people that normally deliver projects, 119:40 119:40 I'm looking at one of those persons is 119:42 119:42 probably going to dissolve away and not 119:44 119:44 exist anymore and get replaced by 119:47 119:47 somebody who is a data person at a 119:49 119:49 computer person, a person that thinks 119:51 119:51 about software programs and things like 119:53 119:53 that. So what I'm basically telling my 119:56 119:56 people is 119:58 119:58 you as an indust as an industry are 120:01 120:01 going to have to evolve. I'm going to 120:03 120:03 have to be having one of my people 120:05 120:05 become more of a data person and more of 120:08 120:08 a technology person and that's going to 120:10 120:10 help us deliver projects in the future. 120:12 120:12 So that's going to help me get that you 120:15 120:15 know basis of the data the eye part of 120:17 120:17 the model to make sure the model works 120:20 120:20 that kind of stuff that is going to be 120:22 120:22 an evolution to our practices. So I 120:24 120:24 think what I'm basically seeing is that 120:27 120:27 we as an industry, a civil engineer 120:29 120:29 needs to be able to think more techy 120:32 120:32 than they did when I first started when 120:34 120:34 I was when I was trained. I was trained 120:35 120:35 and had had a a quarter worth of 120:38 120:38 handdrafting in college. You know, 120:41 120:41 that's going to change. It's going to be 120:43 120:43 a quarter worth of programming, you 120:45 120:45 know, or something like that. We're 120:47 120:47 going to have to change what we do as an 120:48 120:48 a as an industry to kind of adapt to the 120:51 120:51 future. So, I think there is we're going 120:55 120:55 to have to be as civil engineers, that's 120:57 120:57 what I was trained as. We're going to 120:59 120:59 have to be more techy, more techsavvy. 121:01 121:01 It's going to be part of what we are and 121:03 121:03 that's just going to be the future. 121:06 121:06 >> Yeah, 121:07 121:07 I agree. Thanks, Jim. Uh Will, I see 121:10 121:10 your hand up. Go ahead, Will. 121:11 121:11 >> Oh, yeah. I just wanted to uh applaud 121:14 121:14 Jim for his recognition 121:16 121:16 of what he's what he's seeing. Um, full 121:20 121:20 confession, I'm an IT nerd, but 121:23 121:23 part of what is going on within our 121:26 121:26 profession, our industry, is that we are 121:29 121:29 all interconnected. In the past, we 121:31 121:31 would do waterfall. Planning would do 121:33 121:33 planning things, design would do design 121:35 121:35 things, construction would do what they 121:37 121:37 wanted to do, and then maintenance had 121:39 121:39 to figure out what in the world to do to 121:41 121:41 keep the thing together. We're now 121:43 121:43 recognizing, as Jim pointed out, that 121:45 121:45 this is an ecosystem that has all these 121:47 121:47 feedback loops back and forth and around 121:50 121:50 between all these different pieces. And 121:52 121:52 so, you can't do pure design work and 121:55 121:55 then be done with a project. You have to 121:58 121:58 recognize all this interplay back and 122:01 122:01 forth. And so we need the right data to 122:05 122:05 travel with the information as it moves 122:08 122:08 through the different steps of the 122:10 122:10 project and then ultimately to the built 122:12 122:12 asset. So uh again Jim I think you did a 122:16 122:16 great job communicating that and I would 122:19 122:19 encourage all engineers to speak to your 122:22 122:22 peers so that they can hear that you 122:25 122:25 know it doesn't need to sit in a corner. 122:27 122:27 At the same time this is not all an IT 122:29 122:29 thing. It's a we thing, not a not one or 122:33 122:33 the other. 122:38 122:38 >> Thanks, Will. Katie, go ahead, Katie. 122:41 122:41 >> Hi. So, I I totally concur with what the 122:45 122:45 previous 122:47 122:47 um speakers said. Uh I think one of the 122:49 122:49 things that gets overlooked here is data 122:52 122:52 governance um which uh Oklahoma DOT is 122:56 122:56 really making digital delivery work out. 122:60 122:60 And then the second part of that is I 123:04 123:04 think we're lacking just a a basic 123:07 123:07 education on on data. It is we're going 123:10 123:10 from a world where we managed 123:12 123:12 information on paper. Even if your paper 123:15 123:15 was digital, if it was a PDF, we're 123:17 123:17 moving away from information on paper. 123:19 123:19 We're moving to a world of data and 123:22 123:22 manage creating, managing, and sharing 123:26 123:26 data is just completely different from 123:29 123:29 the way you share information that's on 123:31 123:31 paper. 123:36 123:36 >> Yep. 123:39 123:39 Jim, you've uh you've touched uh some 123:42 123:42 things that I think are very close to 123:44 123:44 home with many of us and uh I really 123:46 123:46 appreciate your time and willingness to 123:49 123:49 update us on your efforts um and I I 123:53 123:53 mean I can't can't express how much any 123:56 123:56 more appreciation I think um from myself 123:59 123:59 and from the group and and if there's an 124:01 124:01 opportunity that we can you know engage 124:04 124:04 you further as as you continue to to 124:06 124:06 complete that or make the connections 124:09 124:09 with the the pulled fund studies and 124:11 124:11 others and our discussions with uh BSI 124:15 124:15 and and other things to kind of move 124:18 124:18 this forward more nationally. Uh it 124:21 124:21 seems like we've got some efforts with 124:23 124:23 Brad and Trisha, with Ashtto um to 124:25 124:25 continue that conversation as well. But 124:28 124:28 I think we're excited to see what you've 124:31 124:31 done kind of um be leveraged and adopted 124:34 124:34 uh at a national if not international 124:36 124:36 level. 124:38 124:38 >> Yeah. Good. Thank you. 124:40 124:40 >> Yeah, appreciate it. Thanks again. 124:44 124:44 >> Thanks. 124:54 124:54 All right, Roger. Where? Remind me where 124:58 124:58 we're at. We're to 124:60 124:60 >> Well, I think now we're ready. We have 125:02 125:02 one more presentation 125:04 125:04 um from Oklahoma about their work on 125:08 125:08 their pool fund. And this one we were 125:10 125:10 kind of setting up in two parts 125:12 125:12 potentially to they're going to give a 125:14 125:14 bit of an overview of what they're doing 125:16 125:16 and what they're trying to accomplish. 125:18 125:18 And then we might follow up with a 125:20 125:20 deeper dive at the next session 125:23 125:23 depending on how things come together 125:25 125:25 and what the agenda ends up looking like 125:28 125:28 for the March meeting. But yeah, that's 125:30 125:30 what we talked with with Michael um 125:33 125:33 who's come on here to share with us and 125:36 125:36 with uh with Katie about uh doing. So I 125:41 125:41 see Michael's there. So Michael, you 125:42 125:42 want to take over the presenter role and 125:46 125:46 um share your your slides with us and 125:49 125:49 then we can have some discussion at the 125:52 125:52 end of that. 125:54 125:54 >> Sure thing. 125:56 125:56 Uh can everybody see my screen? 125:59 125:59 We can. 126:00 126:00 >> Yes. Outstanding 126:03 126:03 >> technology win for the day. 126:06 126:06 All 126:07 126:07 >> right. Uh thank you Matt and Roger and 126:09 126:09 of course the committee members for the 126:10 126:10 opportunity to speak. Uh so we're going 126:13 126:13 to get dive right into what we are doing 126:15 126:15 over here in Oklahoma and really start 126:17 126:17 to focus in on those standards 126:20 126:20 development and we're going to sprinkle 126:22 126:22 in a little bit of Star Wars themes. So 126:25 126:25 uh buckle up. 126:29 126:29 So, if we're really going to defeat this 126:30 126:30 dark side of paperbased workflows and 126:32 126:32 disconnected data, we cannot fight 126:35 126:35 alone. Our our mission in Oklahoma, we 126:38 126:38 of course most of us here know we 126:39 126:39 secured the ADCMS grant and I think this 126:42 126:42 is an this as a resource we need to 126:45 126:45 upgrade our fleet. The goal is written 126:48 126:48 in the grant, accelerate the adoption of 126:50 126:50 advanced technology across the entire 126:52 126:52 life cycle from design through 126:54 126:54 construction to operations. 126:57 126:57 It's like a coalition. 126:59 126:59 We aren't the only ones here in this 127:01 127:01 fight. We're joining forces with the 127:03 127:03 other states highlighted here in the 127:04 127:04 first and second round. Um, and just 127:07 127:07 like the alliance needs different ships 127:09 127:09 to fly together, the grant requires us 127:10 127:10 to maximize interoperability. 127:13 127:13 We are building systems to talk to each 127:15 127:15 other, boosting productivity and 127:17 127:17 reducing project delays so we can stay 127:20 127:20 on target. Well, that's kind of like our 127:22 127:22 business case or some might say the 127:24 127:24 badge of honor and is the fuel for our 127:26 127:26 engines. But why? This grant is what 127:31 127:31 pays for the heavy lifting. We will talk 127:33 127:33 about some of those things like we get 127:35 127:35 into the meat of this this presentation 127:36 127:36 a little bit. We're going to talk about 127:37 127:37 our CAD workspace rebuild uh ISO 19650 127:41 127:41 architecture as it comes to our CDE and 127:43 127:43 allows us to move beyond simple 3D 127:45 127:45 modeling and into true interoperability 127:49 127:49 ensuring the data we create and design 127:51 127:51 doesn't die when it hits construction 127:53 127:53 and it survives all the way to 127:54 127:54 operations. 127:57 127:57 Kind of a shout out to Trish. I'm sure 127:60 127:60 she just smiled. And in closing on this 128:02 128:02 slide, I just wanted to say so when you 128:04 128:04 see Oklahoma lit up on this map, know 128:06 128:06 that we're part of the national movement 128:08 128:08 and we are using the federal funds to 128:10 128:10 build a system that is safer, faster, 128:12 128:12 and finally standardized. 128:15 128:15 So this is a little bit of timeline. Um 128:17 128:17 I didn't want to like bury you in 128:19 128:19 timelines, but just want to kind of give 128:20 128:20 you a little bit of uh insight. So this 128:22 128:22 timeline represents our march toward 128:24 128:24 digital delivery. We didn't just guess 128:26 128:26 at the things we needed. We started in 128:27 128:27 2023 with a rigorous gap analysis where 128:30 128:30 we interviewed staff across the 128:32 128:32 enterprise and we found out where the 128:34 128:34 friction points were. We're currently 128:37 128:37 executing our strategic plan. This is 128:39 128:39 where we define the what digital 128:41 128:41 delivery needs to do. And as we move 128:43 128:43 into 2025, we then hit our 128:45 128:45 implementation plan and we're now 128:47 128:47 actually executing on that strategy. 128:51 128:51 Notice the red arrows at the bottom. We 128:53 128:53 are specifically targeting project wise. 128:56 128:56 We identified a lot of gaps there. Uh we 128:58 128:58 wrote some requirements now building out 128:60 128:60 the architecture to support the ISO 129:02 129:02 standards that we are going to discuss a 129:04 129:04 little bit later. And uh what I was 129:06 129:06 mentioning earlier, 129:09 129:09 we all know this feeling as the meme 129:12 129:12 says we altered the project scope. Pray 129:14 129:14 I do not alter it further. In the past, 129:16 129:16 adding additional steps to complete the 129:18 129:18 task felt like it's a hole in our 129:20 129:20 projects or even a scope creep, which it 129:23 129:23 is not. But to stop that, we are 129:26 129:26 bringing order to the galaxy and 129:28 129:28 understanding that these are just 129:29 129:29 additional steps that we have to go 129:31 129:31 through to complete that task in our 129:33 129:33 EDCMS grant. 129:35 129:35 So, we're establishing strict change 129:36 129:36 management, standardizing our processes 129:39 129:39 and data, and we're establishing 129:40 129:40 workforce development and training 129:42 129:42 programs. Just like the Empire runs on 129:44 129:44 strict hierarchy and rules, our new 129:46 129:46 system relies on defined standards so 129:49 129:49 that we do not add additional steps. 129:51 129:51 that's managed, tracked, and doesn't 129:54 129:54 destroy the schedule. 129:59 129:59 See my friends there at the bottom left 130:00 130:00 corner? Why are they high-fiving? It's 130:03 130:03 not just because they finish the job. 130:04 130:04 It's because the first time we're 130:07 130:07 speaking the same language. We often 130:09 130:09 think technology solves problems, but 130:11 130:11 communication is where the projects 130:13 130:13 actually live and die. Phase one, we are 130:15 130:15 teaching our own divisions, Design, 130:17 130:17 Bridge, Rideway, etc. to speak the same 130:19 130:19 common digital language. Phase two, 130:22 130:22 which we're kind of entering now, and or 130:24 130:24 we we entered it and kind of we're like 130:26 130:26 two and a half right now. We extended 130:28 130:28 that language to our consultants and 130:30 130:30 contractors. And in phase three, we're 130:33 130:33 taking ownership of that and moving it 130:34 130:34 into our strategic communications group. 130:38 130:38 If we wait until the end of the project 130:39 130:39 to agree on these terms, we're going to 130:41 130:41 fail. If we pri if, excuse me, we are 130:45 130:45 prioritizing education in common 130:47 130:47 vocabulary, we need to ensure that when 130:50 130:50 we say asset, you know exactly what I 130:53 130:53 mean before a single line is drawn. And 130:56 130:56 hopefully by 20 by the end of 2026, 130:58 130:58 we'll be high-fiving again because we 131:01 131:01 aren't wasting time and translating the 131:02 131:02 data. We're actually moving it. 131:07 131:07 Uh, see the trooper in the bottom left 131:09 131:09 corner? He's fit for duty, but the 131:12 131:12 trooper is useless without those orders. 131:14 131:14 These documents on the screen, these are 131:16 131:16 our general orders. We cannot build a 131:18 131:18 model ready for construction on just ad 131:20 131:20 hoc decisions. We need digital delivery 131:23 131:23 guidelines and modeling standards so 131:24 131:24 everyone can model the same way. Model 131:27 131:27 management plans so we know where the 131:28 131:28 data lives and a responsibil 131:30 131:30 responsibility assignment matrix so we 131:33 131:33 know exactly who's responsible for what 131:36 131:36 data element. Notice you see green cards 131:39 131:39 and yellow cards here. I tried to find a 131:41 131:41 way to kind of show uh where we are on 131:44 131:44 these tasks. Um if you highlight and you 131:47 131:47 look at the yellow cards like say 131:49 131:49 digital delivery guidelines or say 131:50 131:50 roadway modeling standards, we knew that 131:52 131:52 we needed these things but we had to 131:54 131:54 spend a little more time specifically 131:56 131:56 like saying in roadway modeling 131:57 131:57 standards instead of the whole modeling 131:59 131:59 standards to get that out and make sure 132:01 132:01 it's correct. And of course our digital 132:02 132:02 delivery guidelines is yellow. Uh 132:04 132:04 required a little more reading and 132:06 132:06 understanding through our internal and 132:08 132:08 our external engagements. And of course 132:10 132:10 quality management as we can probably 132:12 132:12 imagine uh that's going to take a little 132:14 132:14 bit more time because the technology of 132:16 132:16 where we are and how do we actually re 132:18 132:18 re review a model. 132:23 132:23 My friend over in the left corner, he's 132:25 132:25 now drinking coffee because he knows the 132:26 132:26 heavy lifting is being done by the 132:28 132:28 system and not by manual labor. We're 132:32 132:32 rebuilding the backend to make life 132:34 132:34 easier. 132:36 132:36 Rebuilding CAD workspace so the tools 132:38 132:38 just man they just work. IFC schema 132:41 132:41 integration so exports are automatic and 132:44 132:44 IFC or excuse me ISO 19650 SAS staff 132:48 132:48 certification so our people begin to 132:50 132:50 speak the right language. We're doing 132:53 132:53 the hard work on the project wise data 132:54 132:54 source now so people can sit back sip 132:57 132:57 coffee later knowing the data integrity 132:59 132:59 is actually there and you can you can 133:01 133:01 see that there's some yellow cards here 133:03 133:03 uh for example when we knew we needed 133:05 133:05 some CAD workspace rebuild 133:08 133:08 what we didn't really know was we 133:11 133:11 couldn't really just put a band-aid on 133:12 133:12 it and what we learned we needed to add 133:15 133:15 those additional steps like it's better 133:17 133:17 for us to completely rebuild this thing 133:19 133:19 from the ground up intentionally writing 133:21 133:21 an item types, intentionally putting IFC 133:24 133:24 pieces in there, intentionally writing 133:26 133:26 those reports just to make that data 133:29 133:29 exchange or just reporting back on the 133:31 133:31 data much much easier project-wise. H 133:34 133:34 man, what a beast. But 133:37 133:37 what we learned through that process was 133:39 133:39 again, we couldn't just bandaid it. We 133:42 133:42 couldn't just add a few folders, take 133:44 133:44 some folders out, change some workflow 133:46 133:46 processes. that that thing was set up to 133:49 133:49 deliver paper and what we needed to do 133:52 133:52 was well rebuild it. 133:55 133:55 We'll get into that. 133:59 133:59 Back to our coffee drinker friend on the 134:00 134:00 left. He's effectively he is more 134:03 134:03 effective now because he is looking at 134:05 134:05 uniformity because we established that 134:08 134:08 common language in the back and in the 134:10 134:10 communication phase. We now can build a 134:12 134:12 unified standard workspace. Whether you 134:14 134:14 are in hydraulics or roadway, the 134:16 134:16 environment is locked for consistency. 134:19 134:19 This isn't just about making drawings 134:20 134:20 look the same. It's about making the 134:22 134:22 data behind them consistent. 134:25 134:25 Kind of what Katie was saying before. 134:28 134:28 Because we are uniform internally, we 134:30 134:30 can export item types and IFC 134:33 134:33 externally. We stop being the ragtag 134:35 134:35 rebellion of the different file formats 134:37 134:37 and become a unified force. As you can 134:40 134:40 see, all the different pieces of the the 134:44 134:44 workspaces here. All these disciplines 134:48 134:48 had kind of their own thing going. What 134:49 134:49 we've done by re completely rebuilding 134:52 134:52 it from the ground up. We've unified 134:53 134:53 that standard workspace and now it is 134:55 134:55 fully managed. We're actually in step 134:58 134:58 two now. Now we're starting to expand 134:60 134:60 that workspace and looking at different 135:02 135:02 things. Uh just highlighting NIB's 135:04 135:04 naming convention. One of the things 135:05 135:05 that we did, we gone away from Mike's 135:08 135:08 awesome level number 445 to standard 135:11 135:11 naming conventions for those levels in 135:13 135:13 those codes. So now the data is 135:16 135:16 transportable across state lines. 135:24 135:24 But right now, well, this uh this slide 135:27 135:27 is super technical, but I want to make 135:29 135:29 something very clear. The trooper still 135:31 135:31 relaxed because of the process, not the 135:33 135:33 software. Right now, as we speak, we're 135:36 135:36 writing the architecture document that 135:37 135:37 isn't just 135:39 135:39 a list of IT settings. It's literally 135:41 135:41 the rules of engagement for the next 135:43 135:43 decade of ODOT projects. We're taking 135:45 135:45 the ISO 19650 business processes and 135:49 135:49 hardcoding them into the environment. 135:52 135:52 The philosophy that I'm trying to use 135:53 135:53 here is if we, the owner, don't define 135:56 135:56 our business requirements first, the 135:58 135:58 best software in the world will not save 136:00 136:00 us. So we aren't just installing 136:03 136:03 project-wise, we are configuring it to 136:05 136:05 solve seven specific headaches. We are 136:08 136:08 not putting a band-aid on our current 136:10 136:10 environment. We are establishing a new 136:12 136:12 environment strictly aligned to the ISO 136:14 136:14 19650 standard. 136:18 136:18 To kind of go more in depth of that, a 136:20 136:20 discovery I'd like to say is the data 136:22 136:22 swamp fix. First, we are fixing the 136:25 136:25 where it is problem. 136:27 136:27 Legacy systems force you to dig through 136:29 136:29 say 160 plus folders creating a data 136:32 136:32 swamp. Now we're configuring the 136:35 136:35 attribute-based delivery. We are 136:37 136:37 building the global save searches so you 136:39 136:39 can find the file for what it is not by 136:42 136:42 memorizing where you found it last or 136:45 136:45 memorizing the complex folder path. 136:48 136:48 We are strictly building role-based 136:51 136:51 access control. We are done with 136:53 136:53 managing granular permissions on 136:55 136:55 thousands of folders that leads to 136:58 136:58 permission creep and security risks. 136:60 136:60 Right now we're are mapping user list to 137:02 137:02 the ISO functions such as author, 137:04 137:04 checker, etc. You get added to a list, 137:07 137:07 the system instantly grants you to the 137:09 137:09 exact folder or need to know bases that 137:11 137:11 you need or excuse me the need to know 137:14 137:14 access that you need 137:17 137:17 and trust uh the gated workflow. We are 137:20 137:20 scripting the gated workflow such as 137:23 137:23 work in progress to shared. In the past, 137:25 137:25 you never knew if a file was truly 137:28 137:28 ready. Right now, we are building a 137:30 137:30 system that locks the data. If you see 137:32 137:32 the file in the shared state, you can 137:34 137:34 trust it. The system guarantees it has 137:37 137:37 passed the quality check. 137:40 137:40 And what would it be if we weren't 137:42 137:42 setting up technology? If we didn't have 137:43 137:43 constraints, one of those constraints, 137:46 137:46 we are solving the Windows path limit. 137:48 137:48 Deep folder structures cause the file 137:50 137:50 corruption when they hit 260 characters. 137:53 137:53 We're implementing a fax tonomy. 137:56 137:56 We are intentionally limiting folder 137:58 137:58 depth to prevent those corruption errors 137:60 138:00 from ever happening again. 138:03 138:03 And then we started tackling well what 138:05 138:05 about initiation? What does that look 138:07 138:07 like? 138:08 138:08 We are coding selfservice automation 138:11 138:11 with a thirdparty vendor. We know you 138:14 138:14 hate waiting on IT tickets to just 138:16 138:16 create a project folder. Right now, we 138:19 138:19 are building the automation tool. The 138:21 138:21 model manager fills out a web form and 138:22 138:22 the system instantly builds the 138:24 138:24 compliant ISO 19650 template with all 138:26 138:26 permissions set. No wait times. And that 138:30 138:30 gets us into digital twins readiness. 138:33 138:33 We can probably argue argue on what a 138:35 138:35 digital twin actually is, but in this 138:37 138:37 case, we're ensuring machine 138:39 138:39 readability. Deep folders are dumb. GIS 138:42 138:42 systems can't read them. Right now, we 138:44 138:44 are enforcing the naming convention as 138:47 138:47 the primary key. This means downstream 138:50 138:50 systems like asset management will be 138:51 138:51 able to automatically scrape the spatial 138:53 138:53 code from the file name and map the data 138:56 138:56 without manual entry. 138:58 138:58 So why is a trooper drinking coffee? 139:01 139:01 Because we are doing this heavy 139:03 139:03 architectural lifting now so that when 139:05 139:05 the system does go live, data integrity 139:08 139:08 is automatic. 139:12 139:12 Master Yoda says you must unlearn what 139:14 139:14 you have learned. This is a crit this is 139:16 139:16 critical when we want to talk about the 139:18 139:18 requirements. 139:20 139:20 We are all looking at we are all looking 139:22 139:22 for a version of the ISO 19650 standard 139:25 139:25 in word in words that the United States 139:28 139:28 understands but it does not actually 139:30 139:30 exist. You have to unlearn the idea that 139:33 139:33 there is a single PDF that will solve 139:35 139:35 this problem. 139:36 139:36 There is a trap and I've heard some say, 139:39 139:39 "Well, just give me the 3D model." I 139:41 139:41 need people to unlearn that. If we just 139:44 139:44 treat this as standard as a standard 3D 139:46 139:46 model, we usually get a well a pretty 3D 139:50 139:50 model. But that is not what ODOT needs 139:52 139:52 to run a highway system for the next 50 139:54 139:54 years. 139:56 139:56 We aren't just asking for geometry. We 139:58 139:58 are asking for the data that fuels the 139:60 139:60 op that fuels our operations moving 140:02 140:02 forward. So when you see requirements 140:04 140:04 understand we are moving past just give 140:07 140:07 me that 3D model and asking for data for 140:10 140:10 life cycle decisions 140:15 140:15 and finally distracted by the words you 140:18 140:18 are flow the data it must whether you 140:20 140:20 call it a task team or roadaway squad 140:23 140:23 the deadline doesn't care the data has 140:26 140:26 to move 140:27 140:27 big thanks to the stakeholder group for 140:29 140:29 this opportunity scan the QR code to get 140:31 140:31 in touch with Katie and I. We are here 140:32 140:32 to help you through this transition. 140:35 140:35 May the source of truth be with you. 140:38 140:38 Thank you. 140:41 140:41 >> Thanks, Michael. I uh I can definitely 140:44 140:44 appreciate a good Star Wars tie in uh 140:47 140:47 despite my younger nieces saying it has 140:49 140:49 no relevance anymore. So, 140:52 140:52 I'm not sure that's true. Maybe I'm just 140:54 140:54 getting older. 140:57 140:57 >> Yeah, the fourth was with you there. 141:02 141:02 Yeah, I appreciate it. 141:03 141:03 >> Thank you. 141:03 141:03 >> I try to channel it. 141:09 141:09 >> Um, give any opportunity. Is there any 141:12 141:12 questions for 141:16 141:16 any 141:17 141:17 >> maybe um I could say what we had in mind 141:21 141:21 a little bit Matt and then people are 141:23 141:23 thinking if they have any questions but 141:25 141:25 >> um we Michael and I started talking 141:29 141:29 >> a few weeks ago I guess about you know 141:32 141:32 the idea of doing something with this 141:33 141:33 stakeholder group around this and then 141:36 141:36 um we were thinking that this could 141:40 141:40 potentially be a a workshopping topic or 141:43 141:43 something to go a little bit deeper on 141:46 141:46 this idea of how could we share the 141:49 141:49 common implementation and utilization of 141:52 141:52 ISO 19650 141:54 141:54 because it seems to lie at at the well 141:58 141:58 it lies at the center of what Oklahoma 142:00 142:00 is trying to do and we think there's 142:04 142:04 application for other DOS and so if this 142:07 142:07 standard could be leveraged and used 142:10 142:10 this could be 142:11 142:11 um this could be um something we could 142:15 142:15 collaborate on others. We know there's a 142:17 142:17 few other DOS out there interested in 142:20 142:20 using andor already using ISO 19650 in 142:24 142:24 some way. So we thought we could maybe 142:27 142:27 invite them to um share um if we do that 142:32 142:32 take this topic on at the next workshop 142:34 142:34 or at a future one. Um and we um I I 142:39 142:39 guess myself, you know, I think we we're 142:42 142:42 doing a lot as we've seen with 142:45 142:45 information exchange around IFC, but in 142:48 142:48 order for that to really work at the 142:50 142:50 high level, we need um we need process 142:54 142:54 management standardization or we can 142:57 142:57 benefit from process management 142:59 142:59 standardization 143:00 143:00 as well. And so that would help us 143:03 143:03 utilize all that other good work that's 143:05 143:05 going on even more um thoroughly I think 143:09 143:09 if we if and when we can foster that. 143:13 143:13 Not that we have to do it all through 143:15 143:15 the DDSG, but maybe this is a way to 143:18 143:18 draw attention more attention to it. Um, 143:21 143:21 if we go on from here with uh some more 143:25 143:25 work in a future event 143:28 143:28 if there's interest and uh you know, 143:30 143:30 we're not this is something we can still 143:33 143:33 figure out. But that was some of the 143:35 143:35 thinking between this shorter share 143:38 143:38 today and then potentially more in the 143:41 143:41 future on some of those things that are 143:44 143:44 that need to be done are being done in 143:47 143:47 the grant 143:53 143:53 and I don't know if you want to say 143:55 143:55 anything Michael in addition but um yeah 143:59 143:59 >> no I I appreciate it you know where we 144:02 144:02 were going with the standard and try and 144:03 144:03 align it. Some of the things that we 144:05 144:05 noticed was that is what I kind of keyed 144:08 144:08 in there at the end the terms don't 144:09 144:09 necessarily cross over to United States 144:12 144:12 and uh trying to sift through that and 144:15 144:15 like when we were going through the 144:17 144:17 certification process and our team there 144:19 144:19 was a lot of questions and if anyone's 144:21 144:21 gotten into it what's an appointed party 144:24 144:24 what's the lead appointed party and so 144:26 144:26 on so forth what what is that ne what 144:28 144:28 does that actually mean in US terms uh 144:32 144:32 once we kind of figure that out uh 144:34 144:34 things did start to come together and I 144:35 144:35 would say once actually understanding 144:39 144:39 the standard and applying it to 144:41 144:41 something that's real such as a common 144:42 144:42 or connected data environment 144:45 144:45 it means a lot more Katie. 144:51 144:51 >> Yeah. So, um, totally agree with all of 144:56 144:56 that. And I was just going to say that, 144:57 144:57 you know, the great thing about ISO 144:59 144:59 19650 145:01 145:01 is it is a wellestablished 145:06 145:06 BIM process. So, we don't have to 145:08 145:08 recreate the wheel, right? We can just 145:11 145:11 take what's already been tried and done 145:16 145:16 and we can just apply it to our own 145:18 145:18 environment. It it did get a little bit 145:21 145:21 complicated in the um ISO 19650 training 145:26 145:26 just because um the words were very 145:30 145:30 European and didn't quite exactly 145:32 145:32 translate to the words we use on a daily 145:35 145:35 basis within our DOT to describe the 145:38 145:38 different roles. Um but you know if we 145:41 145:41 can create a crosswalk for that um it 145:44 145:44 becomes a lot more accessible and 145:46 145:46 understandable you know how do we create 145:49 145:49 share and manage this data. 145:54 145:54 I would add part of the process of 145:57 145:57 adapting ISO 19650 for country incountry 146:01 146:01 use is developing a forward and an annex 146:05 146:05 that um identify the places where the 146:08 146:08 language needs to be modified or even 146:11 146:11 the processes need to be modified and 146:14 146:14 that is something we haven't done that 146:15 146:15 here in the US. Um, I know we've done 146:18 146:18 some work on it, um, with Penn State and 146:22 146:22 other people and we're maybe looking to 146:24 146:24 advance that further. So, this could 146:27 146:27 also be a way to help with that language 146:30 146:30 issue. Um, Katie and and figure out a 146:33 146:33 way to do it at a a common national 146:37 146:37 level. 146:42 146:42 Katie and Michael, who who was the ISO 146:46 146:46 19650 training with 146:51 146:51 >> that was a company called Operum 146:54 146:54 Academy. 146:56 146:56 >> Okay. 146:58 146:58 >> And it is that one's based in the UK. Um 147:02 147:02 and I don't think we have any US-based 147:04 147:04 training. 147:09 147:09 And uh we the the fellow from Oper um um 147:14 147:14 Paul Schilcock I think Michael and I 147:16 147:16 were talking with him about potentially 147:19 147:19 giving some kind of abbreviated version 147:21 147:21 of that if we did further with this that 147:24 147:24 you know wouldn't be a full training but 147:26 147:26 that maybe highlight some of those 147:28 147:28 things. He he's very knowledgeable. He 147:31 147:31 was one of the authors of the of the 147:34 147:34 standard. So 147:40 147:40 yeah, there was the comment that Arizona 147:43 147:43 is moving forward. So I think there 147:46 147:46 could be some real opportunity to bring 147:48 147:48 states together around doing this in a 147:52 147:52 in a common way. 147:55 147:55 New Mexico. Great. 147:58 147:58 I think I have heard Calrans is doing 148:01 148:01 something with it. I know there I don't 148:02 148:02 think Devon's here today, but um 148:10 148:10 >> I would love for us to 148:12 148:12 >> Oh, go ahead. 148:16 148:16 >> I think I think it'd be great for us to 148:18 148:18 all get together and dis discuss the 148:20 148:20 ways we can implement this. 148:25 148:25 >> Yeah. Even I mean at a basic level too 148:29 148:29 if we don't have the right terminology 148:31 148:31 or how the US does business is being 148:35 148:35 able to find some resources for some 148:38 148:38 sort of a ISO 19650 primer or 101 that 148:42 148:42 is based on our terminology and and how 148:45 148:45 we do business. 148:59 148:59 Roger who does like if there's a like 149:01 149:01 that you had mentioned I guess like an 149:03 149:03 annex or something that you know for us 149:06 149:06 that we haven't done what's the 149:08 149:08 mechanism to look into something like 149:11 149:11 that 149:12 149:12 >> well the the mechanism is that um um 149:16 149:16 each country um who's a member of ISO 149:19 149:19 which the United States is through the 149:22 149:22 American National Standards Institute 149:25 149:25 establishes mirror committees that 149:28 149:28 mirror the ISO committee at the national 149:31 149:31 level. And in the US, the the uh I the 149:36 149:36 ANIE uh the the the organization that 149:39 149:39 holds the chairmanship for technical 149:42 149:42 committee 59 uh uh subcommittee 13 which 149:46 149:46 19650 is part of is Ashray. 149:51 149:51 um which is the uh uh association of 149:56 149:56 uh um heating and refrigerating uh air 149:59 149:59 conditioning engineers which may not you 150:01 150:01 know be the strongest connection to 150:04 150:04 transportation um and um it hasn't been 150:08 150:08 real active here in the US but um we 150:11 150:11 have recently started working with them 150:14 150:14 and NIBs has taken over being the chair 150:17 150:17 for that committee my colleague uh Jay 150:20 150:20 Klein and we've worked with uh the 150:23 150:23 drafting of Ford and Annex, working with 150:26 150:26 Penn State. So, we're looking to move 150:29 150:29 this stuff forward and that and we want 150:32 150:32 to get more involvement um get that 150:34 150:34 committee um stood up and get more 150:37 150:37 involvement um from the transportation 150:40 150:40 sector in that mirror committee. It's 150:43 150:43 also the committee that votes on, 150:45 150:45 comments on, and votes on all the IFC 150:48 150:48 and IDS and IDM. Every standard that um 150:52 150:52 we use extensively here is under that um 150:56 150:56 committee. So, I think there's some real 150:59 150:59 opportunity for us to build engagement 151:02 151:02 and work on a Ford and annex 151:04 151:04 collectively that could be used here and 151:06 151:06 support transportation in particular. 151:14 151:14 This may be a good item for us to maybe 151:19 151:19 bring up with the members 151:22 151:22 on having 151:24 151:24 a working group uh participate 151:27 151:27 specifically to target 151:30 151:30 that activity and to develop, you know, 151:33 151:33 those kind of documents that we could 151:35 151:35 move forward through the appropriate 151:37 151:37 channels to have that kind of US voice 151:40 151:40 part of international conversation. 151:46 151:46 If there are, you know, members and 151:48 151:48 state agencies that, you know, are on 151:51 151:51 the DASG as members, 151:54 151:54 then we could look to them to, you know, 151:57 151:57 express their interest or be included in 151:59 151:59 those items. 152:09 152:09 Yeah. that that would be great and we 152:11 152:11 could try to collect the states that are 152:13 152:13 working on this uh towards that as well. 152:16 152:16 See, got Arizona and uh New Mexico 152:19 152:19 identified in the chat. 152:23 152:23 >> Yeah. 152:25 152:25 Uh anybody else aware of 152:29 152:29 other 152:30 152:30 agency efforts in this area or interest? 152:35 152:35 You want to drop it in the chat be 152:37 152:37 helpful for us. 152:46 152:46 I think I saw there was New Mexico, 152:48 152:48 Arizona, and then I think we talked 152:50 152:50 about Pennsylvania and California. 152:60 152:60 Trisha says, "Include Minnesota. 153:10 153:10 Okay. Yeah, Roger. Let's um let's figure 153:14 153:14 out a way that maybe we we can 153:17 153:17 get some activity in this area. It seems 153:19 153:19 like it's an urgent kind of kind of 153:21 153:21 baseline item for us in the 153:25 153:25 international sphere as a lot of other 153:27 153:27 activities are moving forward. 153:32 153:32 >> Right. Yeah. Good. I good. That that 153:34 153:34 sounds good. 153:36 153:36 Now, yeah, I thought when I heard about 153:38 153:38 what Oklahoma was doing, it seemed like 153:40 153:40 a good a good way to build on it. So, um 153:46 153:46 >> yeah, and we can we can look at um as we 153:50 153:50 as we work towards the March meeting too 153:53 153:53 and getting our agenda locked down about 153:57 153:57 an expansion either at that meeting from 153:60 153:60 Oklahoma or the the next uh virtual one 154:05 154:05 um as time allows. But let's let's keep 154:07 154:07 that on our radar for the next meeting 154:10 154:10 like you had mentioned already. 154:17 154:17 Okay. 154:21 154:21 Um, let me let's see. I'm typing away on 154:24 154:24 the mural, but let me maybe Well, I 154:26 154:26 guess we can actually I think the next I 154:29 154:29 think we're basically into wrap-up mode. 154:33 154:33 Um, Matt, I don't know if we want to 154:35 154:35 look at the at the draft agenda for 154:40 154:40 March andor the the schedule of events. 154:43 154:43 I could put them up on the mural and 154:46 154:46 that way people could also add comments 154:48 154:48 if they wanted to. So, shall I um take 154:52 154:52 put the mural up with that on it, you 154:54 154:54 think? 154:54 154:54 >> Yeah. Yeah, I think that's the best 154:56 154:56 approach. So that you know again just to 154:60 154:60 reiterate the mural is going to be open 155:02 155:02 and accessible. So um and we are hoping 155:05 155:05 to use that uh to leverage to kind of 155:09 155:09 crowdsource you know um the schedules of 155:14 155:14 other activities bigger conferences 155:18 155:18 um you know for example ASHTTO committee 155:20 155:20 on design ashto committee on 155:22 155:22 construction etc. 155:25 155:25 um 155:27 155:27 to help us with scheduling. Uh there's 155:30 155:30 also um Roger, I think we do have the 155:33 155:33 you know with regards to this slide that 155:36 155:36 mentions the upcoming GIST meeting if 155:39 155:39 there are items of interest from the 155:42 155:42 community with that we tackle. Yeah, 155:46 155:46 Roger's got it on the screen right now. 155:48 155:48 um 155:50 155:50 this meeting number three that we have 155:52 155:52 planned in March. And again, if you want 155:54 155:54 details for any of the meetings and 155:58 155:58 information that we have, they're posted 156:00 156:00 on the DDSG hub um which I have posted 156:08 156:08 again the link in the chat uh to get you 156:11 156:11 there or you can just search TDSGhub 156:15 156:15 uh and it'll get you there as well. Um 156:17 156:17 but in the mural, you know, if there are 156:20 156:20 things that are particular interest, um 156:23 156:23 we are, you know, getting our our legs 156:25 156:25 uh underneath us here with the the group 156:28 156:28 and getting a cadence for our meetings 156:30 156:30 and trying to establish, you know, 156:33 156:33 working items and, you know, priorities. 156:36 156:36 Um but here's the, you know, a good 156:38 156:38 mechanism for us to gain that valuable 156:41 156:41 feedback from everybody, including the 156:43 156:43 DDSG members themselves. Um we do have 156:47 156:47 kind of a a tentative uh high level 156:50 156:50 agenda for the next meeting uh that 156:52 156:52 we're trying to build out. Um, as I 156:56 156:56 mentioned previously, 156:59 156:59 we expect to have some recurring items 157:02 157:02 because of the national prominence of 157:05 157:05 the activity 157:07 157:07 um particularly the pulled fund studies 157:10 157:10 um and all the deliverables and 157:13 157:13 activities that they're taking on both 157:15 157:15 for bridges and for the larger uh BIM 157:18 157:18 for infrastructure which is pretty much 157:20 157:20 everything else except the bridges and 157:23 157:23 structures. 157:24 157:24 And you know th those are a lot of items 157:27 157:27 um 157:29 157:29 in themselves. 157:31 157:31 uh as well as the ADCMS grants. uh other 157:34 157:34 relevant efforts. There are uh plenty of 157:38 157:38 National Cooperative Highway Research 157:41 157:41 Program or NCHRP, 157:43 157:43 national research being done um that tie 157:48 157:48 into digital delivery that I think we 157:51 157:51 should look to have updates on the 157:55 157:55 progress of some of those meetings um as 157:58 157:58 we're allowed to hear those because I 158:00 158:00 know that uh sometimes we have to wait 158:04 158:04 until the project is completed. and the 158:07 158:07 oversight 158:09 158:09 panel for the individual study has 158:13 158:13 approved the deliverables um for 158:16 158:16 publication. But oftent times we're also 158:19 158:19 allowed to get uh information or updates 158:22 158:22 on where they're at with that research 158:25 158:25 or if they're at a point where they're 158:27 158:27 engaging with the larger community to 158:29 158:29 get feedback on draft deliverables. uh 158:32 158:32 oftent time were provided that 158:35 158:35 permission if you will or ability to do 158:38 158:38 that. 158:39 158:39 Um 158:41 158:41 and as well as other efforts that you 158:44 158:44 might be aware of either through 158:47 158:47 uh university um you know many state 158:50 158:50 agencies have research efforts with 158:52 158:52 their universities within their state 158:55 158:55 that are related to digital delivery. So 158:58 158:58 we can certainly entertain um those kind 159:01 159:01 of updates as well as as it applies to 159:04 159:04 digital delivery and its relevance or if 159:06 159:06 they're you know seeking feedback from 159:08 159:08 the community on some of the things that 159:10 159:10 they're delivering whether it's you know 159:13 159:13 guidance documents or other things. Uh 159:15 159:15 that certainly is another area that we 159:17 159:17 can um have as part of our agenda as 159:21 159:21 well. 159:28 159:28 Um few people are signing out. I 159:30 159:30 appreciate them being able to 159:33 159:33 participate. 159:35 159:35 Um 159:38 159:38 we are a little bit ahead of schedule 159:42 159:42 but um yeah and again within the mural 159:45 159:45 uh that Roger showing you know if you've 159:48 159:48 got those any of those events like I 159:50 159:50 said we're we're trying to leverage you 159:52 159:52 to help crowdsource some of these items 159:55 159:55 for our future scheduling. Um our next 159:59 159:59 meeting in March will be the hybrid uh 160:03 160:03 on-site with uh virtual component. Uh 160:07 160:07 the meeting after that will be all 160:09 160:09 virtual again similar to this one. We 160:11 160:11 have not yet established dates for those 160:15 160:15 meetings yet. The next one after that 160:18 160:18 again will be another hybrid inerson. Um 160:22 160:22 we've had some discussion of potentially 160:26 160:26 leveraging uh I HEAP again um event that 160:31 160:31 uh unlike last year which was in October 160:35 160:35 which created some issues because of the 160:37 160:37 budget uh negotiations 160:40 160:40 is uh later in the year at the beginning 160:43 160:43 of December 160:44 160:44 um and Jacob and Texas DOT are actively 160:49 160:49 involved in leading that effort. 160:52 160:52 uh in Austin, Texas. If we end up 160:55 160:55 targeting that one for our next 160:56 160:56 in-person meeting, uh then that's going 160:59 160:59 to put us somewhere in late July for uh 161:03 161:03 another all virtual meeting after March 161:06 161:06 uh to try and kind of accommodate 161:09 161:09 um schedules and make sure we've got a 161:11 161:11 regular cadence. But we're going to comm 161:13 161:13 continue to communicate that with the 161:15 161:15 members as well and get that information 161:17 161:17 out to everybody on the DDSG hub. Um our 161:21 161:21 intent is to get those schedules uh out 161:25 161:25 and locked in uh dates and venues uh 161:28 161:28 much earlier um so that people can plan 161:32 161:32 and have time to plan and get the 161:34 161:34 appropriate approvals for travel. 161:42 161:42 Yeah, I think BIM week was the other 161:44 161:44 event that got some expressions of 161:47 161:47 support as a potential place for 161:51 161:51 as have other ASHTO committee meetings. 161:53 161:53 So, I guess those are things we're going 161:55 161:55 to be working on sorting out. So, if 161:57 161:57 anybody has any thoughts or comments, 162:00 162:00 you can drop them in in the mural over 162:03 162:03 here on the right. Um, 162:07 162:07 that'd be great. 162:09 162:09 Yeah. 162:11 162:11 And um we are a little bit 162:15 162:15 ahead of schedule which is okay. Um I 162:18 162:18 think we all prefer to end earlier than 162:21 162:21 run late. 162:23 162:23 Um just a reminder again we have our 162:25 162:25 next session for the meeting too. Uh 162:29 162:29 third and final session is going to be 162:32 162:32 on Wednesday. If you have not already 162:36 162:36 registered for that event, you can go to 162:38 162:38 the DDSG hub again um through the 162:42 162:42 website uh that I posted um and register 162:46 162:46 for that one. Um we will have our third 162:49 162:49 event uh and we will have both pulled 162:54 162:54 fund studies provide some uh discussion 162:57 162:57 topics there and another ADCMS update uh 163:01 163:01 from Delaware DOT 163:04 163:04 um yeah 163:10 163:10 >> and so we look forward to your continued 163:12 163:12 engagement and participation on 163:15 163:15 Wednesday. 163:19 163:19 >> Yeah, 163:20 163:20 >> I think we have a question from James. 163:26 163:26 Go ahead, James. 163:34 163:34 Or he can he's got his hand raised. Um, 163:37 163:37 if you want to come on and unmute 163:40 163:40 yourself if you got a question or put it 163:42 163:42 in the chat. 163:44 163:44 James is one of the attendees. We see 163:46 163:46 her hand up anyways, unless that's an 163:48 163:48 accident. 163:58 163:58 Well, they they have the option to 163:59 163:59 unmute themselves if they so choose. 164:02 164:02 Accident. Okay. 164:03 164:03 >> All right. Thank you. One thing I will 164:06 164:06 challenge everybody to do before they 164:07 164:07 sign off is uh do go to the mural and 164:10 164:10 and leave a comment um on the general 164:13 164:13 meeting comments for today um maybe if 164:16 164:16 it's just something as simple as you 164:17 164:17 know you like the format, you liked how 164:19 164:19 things were set up, uh things to be 164:21 164:21 improved, uh really anything. Um even 164:24 164:24 just a thanks for the meeting. Uh it 164:27 164:27 would be it's good to fill these out. Um 164:30 164:30 it's nice to get feedback from 164:31 164:31 everybody. So yes, once again, please uh 164:35 164:35 try and uh get on the mural and um I 164:39 164:39 really appreciate it. 164:42 164:42 >> Yep. Uh thanks again on behalf of myself 164:46 164:46 and the digital deliver stakeholders 164:48 164:48 group and we will see you again 164:51 164:51 Wednesday afternoon. 164:53 164:53 >> Yeah, thanks everybody. Thanks 164:54 164:54 presenters. Appreciate your sharing. 164:57 164:57 Yeah, great. Thanks Matt. and be safe 165:00 165:00 shoveling snow if that's where you're 165:02 165:02 going. 165:04 165:04 >> Yes. 165:06 165:06 Thanks. 165:37 165:37 All right, Bradley, I think we're all 165:39 165:39 set for today. 165:41 165:41 >> Yep. I will close the webinar out. 165:45 165:45 >> All right. And um yeah, we'll follow up 165:48 165:48 to get ready for Wednesday. 165:53 165:53 good for today. So, thank you. 165:56 165:56 >> Yep. All right. Thanks everybody. 165:59 165:59 Bye all.