00:15 Good afternoon everybody. We'll get
00:16 

00:16 started just momentarily. Um, usually
00:19 

00:19 takes a minute or so for people to get
00:21 

00:21 pinged their reminders and uh get into
00:25 

00:25 the the room. So um
00:29 

00:29 in just a minute we will get started.
01:09 

01:09 All right. Uh welcome again to the
01:12 

01:12 digital delivery stakeholder group. This
01:14 

01:14 is our third session for our second
01:17 

01:17 meeting. Um
01:20 

01:20 the previous two uh last Thursday and
01:24 

01:24 last Monday um we did have some
01:28 

01:28 adjustments that we had to make due to
01:30 

01:30 the weather and people's schedules and
01:34 

01:34 consistent with that we have some
01:36 

01:36 additional changes today um that we will
01:40 

01:40 get through. Um but quickly just uh our
01:44 

01:44 standard disclaimer with regards to any
01:47 

01:47 of the presentations and discussions
01:49 

01:49 those you know are not any official
01:51 

01:51 positions or uh are meant to infer a
01:55 

01:55 policy requirement or any other kind of
01:58 

01:58 requirement by federal highway or US
01:60 

01:60 DOT. They're really just the presenters
02:03 

02:03 and speakers uh own viewpoint and
02:05 

02:05 opinion and that we do not endorse any
02:09 

02:09 specific products or manufacturers. Uh
02:12 

02:12 if anything is named it's basically
02:15 

02:15 uh for
02:17 

02:17 information exchange and the importance
02:20 

02:20 of the topic being discussed and it
02:22 

02:22 doesn't reflect any endorsement of any
02:25 

02:25 product or entity or name.
02:30 

02:30 And I'm Matthew Corgan. I'm with Federal
02:31 

02:31 Highway Administration. I'm in the our
02:34 

02:34 office of R&D on the infrastructure
02:36 

02:36 analysis and construction team. Um we
02:40 

02:40 have not yet identified a co-chair for
02:42 

02:42 the DDSG. We'll be uh looking to
02:45 

02:45 backfill that gap as quickly as we can
02:48 

02:48 to help facilitate and keep keep us on
02:50 

02:50 task. And additionally, we've got the
02:54 

02:54 National Institute of Building Sciences
02:56 

02:56 support staff, Roger Rackley and Mona,
02:59 

02:59 uh online and helping as well. Um they
03:03 

03:03 have our support contract uh with
03:05 

03:05 Federal Highway Administration for the
03:07 

03:07 execution of the digital delivery
03:09 

03:09 stakeholder.
03:13 

03:13 And we do have an official membership
03:15 

03:15 roster. This is all identified in our
03:18 

03:18 charter as well and on the the website.
03:21 

03:21 Uh we'll provide you the link and
03:23 

03:23 information to that uh as well. We're
03:26 

03:26 going to be brief with some of these
03:28 

03:28 introductory items. Um recognizing that
03:31 

03:31 those of you that have participated in
03:33 

03:33 earlier meetings have seen similar um
03:36 

03:36 but we don't want to leave anybody kind
03:38 

03:38 of out in the dark if you haven't had a
03:40 

03:40 chance to participate previously and
03:42 

03:42 this may be your first time uh online
03:44 

03:44 with us. And if it is your first time,
03:46 

03:46 welcome. Uh these are very much open
03:48 

03:48 meetings and we hope that you'll
03:51 

03:51 participate uh willingly and broadly and
03:54 

03:54 communicate uh via the chat. Um
03:57 

03:57 primarily we can also uh if you've got
04:00 

04:00 questions, you want to come in verbally,
04:02 

04:02 you can raise your hand um and we will
04:05 

04:05 uh recognize you and bring you into the
04:07 

04:07 conversation uh as hands go up and down.
04:10 

04:10 We'll try to keep track of all that in a
04:12 

04:12 timely and efficient manner as we can.
04:15 

04:15 Um, our membership is is a a broad
04:18 

04:18 portion of the digital delivery kind of
04:21 

04:21 uh uh space if you will. We wanted a
04:25 

04:25 variety of stateowner agencies that
04:28 

04:28 represent various regions of the United
04:30 

04:30 States as well as various levels of
04:33 

04:33 maturity within their digital delivery
04:35 

04:35 uh journey. Um and so we have have that
04:38 

04:38 represented as well as some of the uh
04:41 

04:41 related associations.
04:43 

04:43 Um and the associations they designated
04:46 

04:46 their members uh to represent all of
04:49 

04:49 their membership within the association
04:51 

04:51 uh and to keep the the dialogue as well.
04:55 

04:55 Um I will go use this list here just go
04:58 

04:58 down for the sake of roll call for us to
05:02 

05:02 identify who's online. Um and they're
05:05 

05:05 also uh included as panelists, but as a
05:07 

05:07 formality, um Cassidy uh is not here.
05:12 

05:12 That's one of our changes to our agenda.
05:14 

05:14 Cassidy was going to give us an update
05:16 

05:16 on their ADCMS uh project. Um
05:19 

05:19 unfortunately, Cassidy has fallen ill
05:22 

05:22 with something that's going around uh in
05:24 

05:24 that area right now, and she's
05:26 

05:26 unavailable today. Um, next in the list
05:30 

05:30 is uh Rick Bryce.
05:34 

05:34 See Rick online.
05:39 

05:39 Katie.
05:41 

05:41 Is Katie with us today?
05:45 

05:45 Okay.
05:47 

05:47 I'm here. Roger. Check the box. I'm
05:49 

05:49 here.
05:53 

05:53 Cindy
06:00 

06:00 and Will unfortunately had an issue at
06:04 

06:04 home. He's traveling.
06:07 

06:07 Ian
06:09 

06:09 Ian how with building smart
06:16 

06:16 car
06:26 

06:26 Jennifer
06:34 

06:34 Kevin with Ashto
06:41 

06:41 Allan
06:43 

06:43 end up
06:46 

06:46 Roger. People were still shoveling out I
06:48 

06:48 think trying to clear driveways.
06:52 

06:52 >> Um yeah.
06:53 

06:53 >> Yeah. And we had some regrets today with
06:56 

06:56 other meeting conflicts I think too. So,
07:01 

07:01 >> uh, Devin
07:03 

07:03 Devin's here.
07:06 

07:06 I think I see him on the list. Anyways,
07:11 

07:11 thumbs up. All right, Devin.
07:14 

07:14 >> Yeah. Yeah, Deon.
07:16 

07:16 >> Jonathan Quarter.
07:18 

07:18 >> Hey, how's it going everybody?
07:21 

07:21 >> Hey, Jonathan. Welcome back,
07:25 

07:25 Charlie.
07:28 

07:28 Hello.
07:29 

07:29 >> See Charlie.
07:31 

07:31 >> Yeah, Charlie's here. He's online. I I
07:33 

07:33 think I can hear him.
07:35 

07:35 >> Oh, okay.
07:37 

07:37 Okay, good.
07:40 

07:40 >> Thanks, Charlie. Welcome. Um Dan AC
07:49 

07:49 Trisha
07:57 

07:57 Jacob.
07:59 

07:59 >> Good morning y'all. I'm here.
08:01 

08:01 >> Morning Jacob and Brad.
08:05 

08:05 >> Yep. I'm here folks. And just so you
08:07 

08:07 know, Andrew Block from Michigan DOT is
08:10 

08:10 on as well. Um I might have to drop a
08:13 

08:13 little bit early but I'll be
08:14 

08:14 participating.
08:17 

08:17 >> Very good. Yeah, we welcome any
08:19 

08:19 additional staff from the members as
08:21 

08:21 well.
08:23 

08:23 Um thank you. Um
08:27 

08:27 yeah, it's been a challenging few days.
08:29 

08:29 is I know we're just opening up here in
08:32 

08:32 the Washington DC area and uh although
08:35 

08:35 the main interstate roads are fairly
08:38 

08:38 clear and passable, the locals are still
08:40 

08:40 struggling a bit with uh having access
08:43 

08:43 and getting out of neighborhoods. So,
08:46 

08:46 I'm sure there's a lot of that uh
08:48 

08:48 happening in other parts of the country
08:51 

08:51 as well.
08:57 

08:57 Uh and um just a you know brief again
09:00 

09:00 recap of you know why uh we're having
09:04 

09:04 these meetings and it's really a
09:05 

09:05 collaborative effort. Uh we want to
09:08 

09:08 coordinate the diverse activities and
09:11 

09:11 efforts that are being done around the
09:13 

09:13 United States with regards to digital
09:15 

09:15 delivery. um
09:19 

09:19 primarily to make sure that we've got an
09:21 

09:21 understanding of where everybody's at,
09:24 

09:24 where potential gaps andor challenges
09:27 

09:27 might be occurring. Um where we may need
09:30 

09:30 to focus uh some early efforts or bring
09:33 

09:33 some resources or find and leverage
09:35 

09:35 resources to address issues uh in order
09:38 

09:38 to help everybody advance and progress
09:40 

09:40 forward. and also uh to ensure there
09:44 

09:44 isn't a lot of duplication of efforts.
09:46 

09:46 We want to make sure that people are
09:48 

09:48 able to learn and leverage and utilize
09:51 

09:51 the experiences and things that are
09:53 

09:53 being developed um by their colleagues
09:56 

09:56 around the country as well. Uh it is an
09:58 

09:58 open group um as I've mentioned with a
10:02 

10:02 very diverse range of of both members
10:05 

10:05 and other participants. So we encourage
10:08 

10:08 that collaboration and dialogue and and
10:10 

10:10 again happy that that you're all um
10:14 

10:14 taking the time to join us today and
10:16 

10:16 blessed to have you involved. So, please
10:20 

10:20 feel free to have that open dialogue and
10:22 

10:22 provide uh any comments or questions or
10:26 

10:26 raise your hand as as needed moving
10:28 

10:28 forward.
10:31 

10:31 Um so the revision to the agenda again
10:34 

10:34 um we do have uh advanced
10:38 

10:38 digital construction management systems
10:41 

10:41 uh grant projects that have been
10:43 

10:43 initiated around the country various DOS
10:45 

10:45 and we were going to have an update uh
10:48 

10:48 similar to what we did in one of our
10:50 

10:50 earlier uh sessions for meeting two um
10:55 

10:55 an update from uh Delaware on their
10:57 

10:57 ADCMS project uh Unfortunately, with
11:00 

11:00 Cassid's illness, um she had to drop
11:03 

11:03 out. Uh and so we wish her um uh good
11:08 

11:08 health and a quick recovery and uh I'm
11:11 

11:11 sure we'll have an opportunity moving
11:13 

11:13 forward to to get that update uh from
11:15 

11:15 her as well as other projects moving
11:18 

11:18 forward. Um so the crux of our meeting
11:21 

11:21 today is going to be getting some uh
11:24 

11:24 information and some dialogue with the
11:26 

11:26 two major uh BIM related transportation
11:30 

11:30 pulled fund projects or TPFs. We have
11:33 

11:33 the uh BIM for bridge which uh is phase
11:37 

11:37 two uh pulled fund study as well as the
11:40 

11:40 BIM for infrastructure or uh BIM 4 II or
11:44 

11:44 BFI um nomenclature. uh we will spend
11:48 

11:48 our meeting um giving some
11:50 

11:50 presentations, updates and having
11:51 

11:51 dialogue
11:53 

11:53 uh with those two entities. This will
11:56 

11:56 likely to be a a recurring kind of
11:58 

11:58 agenda item uh because of the importance
12:01 

12:01 of those transportation pulled funds,
12:03 

12:03 the number of agencies that have
12:06 

12:06 contributed monetarily and are involved
12:10 

12:10 uh in overseeing those pulled funds and
12:12 

12:12 directing them, all the deliverables
12:14 

12:14 that are being developed and uh out of
12:16 

12:16 those efforts. Uh so we expect to have a
12:19 

12:19 a regular cadence of interactions with
12:21 

12:21 the pool funds um to understand what
12:25 

12:25 they're doing and also for them to
12:26 

12:26 engage us and you know how we can help
12:29 

12:29 or if we need to provide any uh
12:32 

12:32 additional dialogue or feedback on on
12:34 

12:34 those activities as well. So we may we
12:38 

12:38 may end early. Uh I hope that is okay.
12:41 

12:41 Typically, it's uh people don't complain
12:44 

12:44 whenever we end early versus uh running
12:46 

12:46 over. Um but uh we also want to make
12:50 

12:50 sure that we do have plenty of time for
12:52 

12:52 that dialogue and and uh have a a
12:55 

12:55 thorough conversation. So we we may not
12:58 

12:58 end early. I'm not exactly sure. Um
13:04 

13:04 we have uh launched our website the uh
13:08 

13:08 digital delivery stakeholder group hub.
13:10 

13:10 Um, you can find it at this uh website
13:14 

13:14 here. Um, I am
13:19 

13:19 also going to try and put that on the
13:24 

13:24 uh chat
13:29 

13:29 so that you can just link to it.
13:33 

13:33 Um but if you go there uh this is where
13:37 

13:37 we'll post all the information upcoming
13:39 

13:39 meetings how you can register for those
13:41 

13:41 meetings. Our next uh inperson meeting
13:45 

13:45 which will also have a virtual component
13:47 

13:47 so in a hybrid format is scheduled in
13:50 

13:50 March. You can find the links to
13:53 

13:53 register for those. There are two
13:54 

13:54 separate links for that meeting. If you
13:57 

13:57 are going to be participating virtually
14:01 

14:01 um from your home location then uh
14:03 

14:03 there's a set of links there. If you are
14:05 

14:05 going to be on site and joining us uh at
14:09 

14:09 the venue that the GIST
14:12 

14:12 uh meeting is being held um then there's
14:14 

14:14 a separate set of links to register
14:16 

14:16 there as well. Um we will be posting
14:19 

14:19 resources there. Uh you will find the
14:21 

14:21 charter there and the details about the
14:23 

14:23 group and why it was established. Um
14:26 

14:26 you'll also find recordings from uh the
14:30 

14:30 previous meetings. Uh we'll continue to
14:32 

14:32 update those recordings and
14:34 

14:34 presentations to make them accessible um
14:37 

14:37 moving forward as well as additional
14:39 

14:39 dialogue and and resources uh as as we
14:43 

14:43 you know gain momentum and and continue
14:45 

14:45 with our efforts. We do envision this to
14:47 

14:47 be a long-term effort. Um and we'll have
14:51 

14:51 uh generally targeting about four
14:53 

14:53 meetings uh per week where we will have
14:56 

14:56 a set of just virtual meetings and then
14:59 

14:59 in between a hybrid in person plus
15:01 

15:01 virtual meeting
15:05 

15:05 and
15:08 

15:08 you know
15:09 

15:09 not to go into a lot more detail because
15:12 

15:12 we have covered this several times. Um,
15:14 

15:14 but we do have the charter uh again
15:16 

15:16 online that u mentions the purpose and
15:19 

15:19 objectives and scope and and how we're
15:22 

15:22 going to kind of operate uh moving
15:24 

15:24 forward. You can access that through the
15:26 

15:26 the DD uh SG hub um at the previous
15:32 

15:32 website. Uh there is the link to the
15:34 

15:34 direct charter, but you can find it
15:36 

15:36 through the the DDSG hub uh quite easily
15:39 

15:39 and get into those details. I would
15:41 

15:41 encourage you to review those um if
15:43 

15:43 you've got any questions as far as you
15:45 

15:45 know what we're trying to do here. But
15:47 

15:47 but again it's really the objective is
15:49 

15:49 to foster that collaboration and
15:50 

15:50 knowledge sharing uh so that we can
15:53 

15:53 progress collaboratively
15:55 

15:55 uh in a very targeted manner um uh in
15:58 

15:58 the digital delivery space recognizing
16:00 

16:00 that there's a lot of activities going
16:02 

16:02 on in this space um and a various levels
16:06 

16:06 of maturity as well. And so uh we're
16:08 

16:08 going to try and coordinate uh a lot of
16:11 

16:11 diverse topics in and areas whether it's
16:13 

16:13 the transportation pulled funds um the
16:16 

16:16 other national research efforts that are
16:19 

16:19 related to digital delivery from
16:21 

16:21 national cooperative highway research
16:23 

16:23 program or NCHRP projects uh as well as
16:26 

16:26 other uh research that's being done
16:28 

16:28 either through uh state agencies or that
16:32 

16:32 they funded through their academic
16:34 

16:34 institutions within their state. Um, and
16:36 

16:36 we do have some uh as well that federal
16:39 

16:39 highway through through uh our location
16:42 

16:42 here, our research uh and development
16:44 

16:44 campus here at Turner Fairbank Highway
16:46 

16:46 Research Center uh in the Northern
16:48 

16:48 Virginia part of the Washington DC uh
16:52 

16:52 DMV.
16:54 

16:54 Oh,
16:58 

16:58 we will continue using Mural as a as a
17:01 

17:01 way to engage and get information from
17:04 

17:04 you. Uh we've got some good feedback so
17:07 

17:07 far uh the last few sessions on the
17:10 

17:10 mural. Um the uh link is here. Um
17:17 

17:17 and I can do Yeah. And uh Rackley,
17:21 

17:21 thanks for putting that in the chat as
17:22 

17:22 well for anybody to access. Um, if you
17:26 

17:26 go into the mural, uh, you'll see uh
17:30 

17:30 various uh slides, if you will, or
17:33 

17:33 presentation formats for you to be able
17:36 

17:36 to engage with us. Um, the three
17:39 

17:39 columns, um, today's meeting is on the
17:43 

17:43 far right of the three columns. When you
17:45 

17:45 go in, it will, uh, ask you if you want
17:48 

17:48 to, you know, use a registration or to
17:51 

17:51 come in as a visitor. You can come in as
17:53 

17:53 a visitor. we would prefer and we would
17:56 

17:56 like for you to identify yourself and at
17:58 

17:58 least type your name and not just be
17:60 

17:60 anonymous, but if you do choose to be
18:01 

18:01 anonymous, that's okay as well. Um, but
18:04 

18:04 it helps us to kind of understand the
18:06 

18:06 perspectives, you know, knowing who you
18:08 

18:08 are and where you're from. Um I will
18:11 

18:11 turn it over to Rackley if um Rackley if
18:15 

18:15 you want to go and kind of share the
18:17 

18:17 mural page and um when people come in
18:20 

18:20 and and how they can either follow you
18:22 

18:22 or um uh turn off their pointer uh so we
18:27 

18:27 don't have a whole lot lot of pointers
18:30 

18:30 flowing through etc. I'll stop sharing
18:32 

18:32 and let you come in and do that.
18:36 

18:36 >> And we we do have maybe Rackley can
18:39 

18:39 conduct it now. We do have a poll too to
18:42 

18:42 check on the demographics of our
18:44 

18:44 participants. So maybe we can weave that
18:48 

18:48 into this session with the mural and get
18:51 

18:51 it too.
18:53 

18:53 >> Right.
18:55 

18:55 >> Thanks for that reminder, Roger. I uh
18:57 

18:57 completely forgot about the
18:58 

18:58 demographics. I should have hit that
18:60 

18:60 earlier, but we'll do that after we get
19:02 

19:02 through the mural, I think.
19:03 

19:03 >> Yeah, it's all good.
19:06 

19:06 >> Let's see. Is this sharing correctly?
19:19 

19:19 >> Is it sharing correctly?
19:21 

19:21 >> I think it's trying to Yeah, it's coming
19:23 

19:23 through now, Rackley. Yep, we see it.
19:25 

19:25 >> Awesome.
19:27 

19:27 So, uh, welcome to the mural. Um, a
19:30 

19:30 couple important ground rules for this.
19:32 

19:32 When you first join, um, at the bottom
19:35 

19:35 of the screen, you'll see a list of
19:36 

19:36 participants. Uh, either people who have
19:38 

19:38 identified themselves or, um, you know,
19:41 

19:41 people who are anonymous.
19:42 

19:42 >> Uh, very important thing that you should
19:44 

19:44 do is you should scroll over your own
19:45 

19:45 name and deselect broadcast my cursor.
19:50 

19:50 Um, it's very difficult to see all the
19:52 

19:52 different items we have in this mural uh
19:55 

19:55 when there are all these different
19:56 

19:56 cursors zooming around as Matthew said.
19:59 

19:59 So, please do that when you first join.
20:02 

20:02 Uh, another thing to note is like
20:05 

20:05 Matthew had mentioned when you leave a
20:07 

20:07 sticky note which you can do by double
20:09 

20:09 clicking it'll create a sticky note. You
20:11 

20:11 can change the color of it. Um, you can
20:13 

20:13 change your text size all in this
20:14 

20:14 ribbon. Um that's how you'll leave a you
20:17 

20:17 know a helpful uh comment
20:22 

20:22 and you can sign it with your name if
20:23 

20:23 you want to or you can leave it
20:25 

20:25 anonymous. Um whatever makes you most
20:28 

20:28 comfortable for leaving feedback. Um
20:30 

20:30 these sticky notes you can place them uh
20:34 

20:34 anywhere but is preferred. As we see
20:36 

20:36 here today's meeting we have a couple of
20:38 

20:38 uh defined areas for that. Uh so here we
20:42 

20:42 have our our meeting agenda for today.
20:43 

20:43 Of course, you know, things have been
20:44 

20:44 altered. Uh we have a link to the FHWA
20:48 

20:48 DDSG website. Um this whole image is a
20:51 

20:51 link. You can click on this open section
20:53 

20:53 here. Uh if you want updates to the
20:55 

20:55 DDSG, uh or or updates for what we're
20:58 

20:58 doing, uh you can also subscribe to that
20:60 

20:60 here. It will take you to a simple form.
21:02 

21:02 Uh I will be collecting
21:05 

21:05 um
21:09 

21:09 links that are pasted in the chat today.
21:10 

21:10 if they're relevant to presenters
21:12 

21:12 speaking everything they will be posted
21:14 

21:14 here. Um if you would like to leave
21:17 

21:17 comments, questions, concerns, uh you
21:19 

21:19 can leave them here in this general
21:21 

21:21 meeting comment section. Um yeah, just
21:23 

21:23 double click anywhere and you can you
21:25 

21:25 know type out your your type out your
21:27 

21:27 comment there and um that would be very
21:29 

21:29 helpful. I would encourage everybody to
21:31 

21:31 leave at least one comment somewhere on
21:32 

21:32 any of these subsections for today. Um
21:35 

21:35 it's really appreciated. Uh this mural
21:37 

21:37 will be permanent. uh you will always be
21:39 

21:39 able to access it and we will use mural
21:42 

21:42 for uh future meetings. So this is a a
21:44 

21:44 space for you to uh collaborate with
21:47 

21:47 your peers and other members of the
21:48 

21:48 DDSG. Um so yes once again prefer
21:52 

21:52 comments to be
21:57 

21:57 to the mural today
21:59 

21:59 >> you can see oh sorry I was going to
22:01 

22:01 point out you can see in in in the mural
22:03 

22:03 the the um last two days meetings as
22:08 

22:08 well and the comments and things people
22:10 

22:10 left.
22:11 

22:11 >> Correct.
22:14 

22:14 As you can see in these other two
22:15 

22:15 columns, we have from our first session,
22:17 

22:17 we uh got a lot of comments on on
22:19 

22:19 different subsections and slides and
22:21 

22:21 things and uh on our uh schedules and
22:23 

22:23 everything. Um so yet you can go back
22:26 

22:26 and feel free to explore all those
22:27 

22:27 options as this current meeting goes on
22:28 

22:28 or later. Um but I would encourage you
22:31 

22:31 to today on one of our subsections do
22:34 

22:34 leave a comment. Um even if it's just
22:36 

22:36 hey I like this or hey I don't like
22:38 

22:38 this. Um that would be really
22:40 

22:40 appreciated.
22:43 

22:43 Are there any questions on Mural? I know
22:45 

22:45 some people will have issues. Uh their
22:48 

22:48 organization may block access to Mural.
22:51 

22:51 Um unfortunately that's not something we
22:53 

22:53 can help you with. You would have to
22:54 

22:54 discuss that with your IT to get access.
22:57 

22:57 You could also use a personal email
22:58 

22:58 however to to get around that. If you're
23:00 

23:00 using your um
23:02 

23:02 uh organization's email address to
23:04 

23:04 login, you could use a personal one and
23:06 

23:06 then leave comments here. Um that's one
23:08 

23:08 way to get around that. But as far as
23:10 

23:10 organization emails, that's you'll have
23:11 

23:11 to take it up with them.
23:14 

23:14 Let's see. Are there any
23:17 

23:17 comments
23:19 

23:19 >> the people too? Don't be afraid to just
23:20 

23:20 jump in there and use it. You can't hurt
23:22 

23:22 anything. Um the the the frame of it is
23:26 

23:26 locked down. So you can't delete uh
23:29 

23:29 anything. If you make a comment, you can
23:32 

23:32 delete it always by highlighting it and
23:35 

23:35 deleting it if you made a mistake. Um or
23:38 

23:38 you can move it by um right clicking on
23:42 

23:42 it and selecting the move from the menu
23:44 

23:44 up above if if you got it in the wrong
23:47 

23:47 place or something. So um
23:52 

23:52 it's pretty good once you get on to it.
23:55 

23:55 So good for for sharing.
23:59 

23:59 >> Yeah, absolutely.
24:01 

24:01 So I will stop sharing my screen.
24:04 

24:04 We will um
24:06 

24:06 we'll do the poll pretty soon here. The
24:09 

24:09 demographic poll.
24:12 

24:12 >> Yeah, I think we can do that now. Are we
24:13 

24:13 going to um set it up correctly?
24:17 

24:17 >> Yep. I will launch it now.
24:21 

24:21 Are you all able to see this?
24:26 

24:26 I'm hoping for at least 80 85%
24:28 

24:28 participation. uh 100% would be
24:31 

24:31 fantastic, but you know, we have to be
24:33 

24:33 realistic about these things.
24:44 

24:44 And um Mackley, I think you said this
24:46 

24:46 the other day that hosts and panelists
24:50 

24:50 cannot
24:51 

24:51 use the poll.
24:56 

24:56 Yeah. Oh, it says so right on the panel.
24:58 

24:58 Okay, good.
25:06 

25:06 But we know who they are, who we are. So
25:10 

25:10 >> that makes sense.
25:12 

25:12 >> This just gives us a good idea who our
25:14 

25:14 audience is and we try to, you know,
25:17 

25:17 ensure that we're having that broad
25:19 

25:19 dialogue with various parts uh of the
25:22 

25:22 industry, transportation,
25:30 

25:30 We'll leave it up for a little while
25:32 

25:32 here to make sure we can get a good
25:34 

25:34 response.
25:36 

25:36 And Rocky, when you think things have
25:39 

25:39 kind of trailed off, you can go ahead
25:42 

25:42 and close it.
25:45 

25:45 Okie dokie. Are there any questions so
25:48 

25:48 far about mural or um any other manner
25:51 

25:51 in which we communicate? I know there
25:54 

25:54 was an issue earlier in the settings for
25:56 

25:56 these Zoom meetings. I have it on by
25:58 

25:58 default that attendees can can chat with
25:60 

26:00 everybody, but despite that, I am having
26:02 

26:02 to manually allow it. So, I know in the
26:05 

26:05 beginning there might have been an issue
26:06 

26:06 with people uh not being able to use the
26:08 

26:08 chat, but I think that's reserved now or
26:10 

26:10 uh resolved now.
26:13 

26:13 I think everybody should be able to to
26:15 

26:15 uh use the chat. Make sure that you know
26:18 

26:18 where it says type message here, right
26:19 

26:19 above that, it's two. you can select
26:21 

26:21 everyone uh so that your questions are
26:23 

26:23 seen by everybody. Uh I think by default
26:25 

26:25 it might just be two hosts and
26:27 

26:27 panelists. Um
26:29 

26:29 I don't think that's a setting that I
26:31 

26:31 can alter. So if you want to pose your
26:33 

26:33 question to everyone. Uh please do
26:35 

26:35 select that.
26:38 

26:38 >> Yeah. Thanks Rackley. Yeah. And you know
26:41 

26:41 again as a reminder the mural board will
26:44 

26:44 be a living document. So, if you've got,
26:47 

26:47 you know, a thought that comes up after
26:48 

26:48 the fact, um, or after the meeting or,
26:52 

26:52 oh boy, I wish I would have, you know,
26:53 

26:53 shared that information, um, you know,
26:56 

26:56 you can still come into to the mural,
26:59 

26:59 um, and it will be available. The one
27:02 

27:02 area um, in particular that we would
27:06 

27:06 definitely like your uh, feedback on
27:09 

27:09 would be um, towards the bottom of
27:13 

27:13 today's meeting. uh items on mural,
27:15 

27:15 you'll see the DDSG
27:17 

27:17 schedule and events and it points over
27:20 

27:20 to the middle column and the bottom
27:23 

27:23 slide area. Um, we're just trying to
27:25 

27:25 kind of crowdsource and get an idea of
27:28 

27:28 the industry events or large meetings
27:30 

27:30 and conferences uh that are uh upcoming
27:34 

27:34 this year for us to be able to
27:36 

27:36 coordinate uh our schedules and
27:38 

27:38 potential locations or where we might be
27:41 

27:41 able to collaborate with another meeting
27:43 

27:43 or or you know entity. Um if you are
27:48 

27:48 aware of any uh large events, meetings,
27:52 

27:52 conferences or things that particularly
27:54 

27:54 ones you're going to be attending and
27:57 

27:57 you know would either not be available
27:59 

27:59 or um you know potentially could be at a
28:02 

28:02 venue that we could reach out to to
28:04 

28:04 collaborate on. If you could go ahead
28:06 

28:06 and just add that um in with a sticky
28:09 

28:09 note, uh be very much appreciated. Um,
28:12 

28:12 we're going to try and leverage the
28:14 

28:14 mural uh for that crowd sourcing effort
28:16 

28:16 to to help us with scheduling moving
28:18 

28:18 forward as well.
28:23 

28:23 >> Okay, I think we I'm going to close out
28:26 

28:26 the poll now. Speak now forever. Hold
28:28 

28:28 your peace.
28:31 

28:31 Okay,
28:36 

28:36 so these are the results mostly state
28:38 

28:38 DOT um consultants and FHWA members
28:42 

28:42 although we do have some technology
28:44 

28:44 member vendors and some others um but
28:47 

28:47 mostly state DOT
28:60 

28:60 Um so uh as I mentioned um you know we
29:03 

29:03 did we did have a a bit of a change. I
29:06 

29:06 appreciate again everybody's grace and
29:09 

29:09 uh willingness to to be agile and
29:12 

29:12 rearrange things for all three of these
29:15 

29:15 sessions. Uh particularly with the the
29:17 

29:17 way the weather has been and other
29:19 

29:19 people's dynamic schedules, um we
29:22 

29:22 recognize that everybody is very busy
29:24 

29:24 and there's a lot of things going on. Um
29:27 

29:27 and it's often hard to carve out uh some
29:29 

29:29 dedicated time. And so that was one of
29:32 

29:32 the reasons we broke this second meeting
29:35 

29:35 into three uh sessions of smaller blocks
29:37 

29:37 to try and help in that area versus our
29:40 

29:40 in-person meetings that will be more of,
29:43 

29:43 you know, a day or multi-day uh format
29:46 

29:46 dedicated at one location. Um, we'll
29:50 

29:50 continue to, you know, engage our
29:51 

29:51 membership and get feedback on what, you
29:54 

29:54 know, is the most appropriate or how we
29:56 

29:56 can make sure that we get the broadest
29:58 

29:58 engagement and can accommodate
29:60 

30:00 everybody's schedules. and uh intend to
30:03 

30:03 get uh future meeting dates and
30:05 

30:05 locations locked down uh as early as we
30:09 

30:09 can, much earlier than we've been able
30:11 

30:11 to so far as we've gotten our legs under
30:13 

30:13 us and and get get a cadence um to make
30:16 

30:16 sure that we've got information and
30:18 

30:18 resources out to everybody to be able to
30:20 

30:20 schedule for their travel uh or get
30:23 

30:23 appropriate approvals. Um but uh the the
30:26 

30:26 primary uh agenda item for today is on
30:31 

30:31 the two transportation pulled fund
30:32 

30:32 studies or TPFs.
30:35 

30:35 Um I do have links that I'll drop uh
30:38 

30:38 into the chat for all of those pulled
30:41 

30:41 fund studies as background. Um but I
30:44 

30:44 will turn it over Roger to you to kind
30:46 

30:46 of uh tee up the conversation and uh
30:50 

30:50 bring people online.
30:52 

30:52 >> Thanks Matt. Um yeah, so um we've been
30:56 

30:56 um working with the pool funds to
30:59 

30:59 determine the you know they're they have
31:02 

31:02 within their goals the needs to interact
31:05 

31:05 with stakeholders communicate with uh
31:08 

31:08 with industry and with peer
31:11 

31:11 organizations and other DOS and um in
31:15 

31:15 industry industry organizations as well
31:18 

31:18 as um what the digital delivery
31:21 

31:21 stakeholder group is set up to do. And
31:24 

31:24 so we've been working with them to
31:26 

31:26 identify their needs and requirements so
31:30 

31:30 we could all collaborate together on the
31:32 

31:32 the best way to um manage what needs to
31:38 

31:38 be done and share and collaborate and
31:40 

31:40 find the best place to do it. identify
31:43 

31:43 those things that are most appropriate
31:45 

31:45 for the digital delivery stakeholder
31:47 

31:47 group to take lead and responsibility
31:50 

31:50 for and which are better left to the
31:53 

31:53 poolled funds and uh keep that dialogue
31:56 

31:56 going. And so we've we talked about this
31:60 

31:60 some um uh during BIM week with the
32:02 

32:02 poolled funds and we wanted to like give
32:05 

32:05 them a chance to share their thoughts
32:08 

32:08 about their needs and requirements so
32:10 

32:10 that the digital delivery stakeholder
32:12 

32:12 group members and community could hear
32:16 

32:16 those and help us to figure out the best
32:19 

32:19 way to um take advantage of these things
32:23 

32:23 we're all trying to do. Leverage them.
32:26 

32:26 avoid duplication and and hopefully make
32:29 

32:29 as efficient as possible and as valuable
32:32 

32:32 as possible use of everyone's precious
32:35 

32:35 time. So, we're going to hear from both
32:38 

32:38 pool funds today. Um from BIM for
32:41 

32:41 Bridge, I think um uh Julie Rivera is
32:44 

32:44 going to present and there's other
32:46 

32:46 representatives here and they can
32:48 

32:48 introduce themselves when they start and
32:50 

32:50 then once they're done um we'll have BIM
32:53 

32:53 for infrastructure present. I think um
32:56 

32:56 I'm not sure who's leading that. Uh I
32:59 

32:59 think John Wilkerson and he he he can
33:02 

33:02 introduce the other
33:04 

33:04 infrastructure members here and then
33:06 

33:06 we'll have some open discussion at the
33:09 

33:09 end. Um and I think the or is the order
33:12 

33:12 still okay uh Julie and John to start
33:15 

33:15 with bridge and go to infrastructure?
33:19 

33:19 >> Yes. and we will start with an overview
33:21 

33:21 that Thomas Hamsky from Iowa DOT will
33:23 

33:23 give but essentially yes this is the
33:25 

33:25 correct order and we've got a a unified
33:27 

33:27 plan here
33:29 

33:29 >> I know you guys have been talking and
33:31 

33:31 working together on this so yeah it's
33:34 

33:34 great to have everybody um here and able
33:37 

33:37 to share and discuss so um shall we turn
33:42 

33:42 would you want to present Julie is
33:44 

33:44 Thomas gonna present
33:46 

33:46 >> I will share my screen and Thomas will
33:48 

33:48 get us um kicked off.
33:50 

33:50 >> Yep.
33:51 

33:51 >> Okay, great.
33:52 

33:52 >> Sorry, really quick. I think we have a
33:54 

33:54 raised hand. Uh, Irwin, is that on
33:57 

33:57 purpose? Do you have a question or is
33:59 

33:59 this an accident?
34:06 

34:06 You can unmute if if that's if you do
34:09 

34:09 have a question.
34:11 

34:11 >> Is it a presenter or I mean one of our
34:13 

34:13 panelists? Rack,
34:14 

34:14 >> that's an attendee. Attendee.
34:17 

34:17 >> Okay.
34:21 

34:21 it.
34:23 

34:23 Well, I guess it might have been a uh
34:26 

34:26 mistake.
34:28 

34:28 Yeah, if if it isn't, we can come back
34:30 

34:30 to it andor um they can um give us uh
34:35 

34:35 put it in the chat. So,
34:42 

34:42 >> okay. Shall I
34:43 

34:43 >> All right, Thomas, welcome.
34:46 

34:46 >> All right. Thank you very much. Um my
34:47 

34:47 name is Thomas Hamsky. I work for Iowa
34:49 

34:49 Department of Transportation. I am part
34:51 

34:51 of the executive committees of both uh
34:53 

34:53 pulled funds uh BIM for Infrastructure
34:54 

34:54 and BIM BIM for Bridges and Structures.
34:57 

34:57 Um I'll be presenting to recently stated
34:60 

34:60 with John Wilkerson from BIM for
35:01 

35:01 Infrastructure and Julie Rivera from BIM
35:03 

35:03 for Bridges respectively. Uh next slide.
35:05 

35:05 Julie,
35:08 

35:08 do the two of you want to introduce us
35:09 

35:09 real introduce yourselves real quick
35:11 

35:11 before we dive in?
35:14 

35:14 Sure,
35:17 

35:17 I can introduce myself. Uh, let me turn
35:19 

35:19 on my camera as well.
35:23 

35:23 There we go. Hello everyone. I'm Julie
35:26 

35:26 Rivera from HDR. I'm the project manager
35:29 

35:29 for the consultant team that's leading
35:30 

35:30 the BIM for Bridges and Structures
35:32 

35:32 effort.
35:34 

35:34 >> John Wilkerson. I'm the digital delivery
35:36 

35:36 director for Michael Baker
35:38 

35:38 International. Um we're team with uh WSP
35:42 

35:42 uh making up BM launch alliance uh
35:44 

35:44 leading the BEM infrastructure pool.
35:48 

35:48 >> Thanks John Julie. So this this morning
35:50 

35:50 or afternoon whatever time zone you're
35:52 

35:52 in we're going to be talking we're
35:53 

35:53 briefly uh going to give I will give a
35:55 

35:55 brief overview of the pulled funds. I
35:57 

35:57 know in our last meeting for the DDSG a
35:60 

35:60 heap uh I know I presented on BIM for
36:02 

36:02 infrastructure and I think will sharper
36:04 

36:04 presented on BIM for bridges structures
36:06 

36:06 but we just want to give another uh
36:08 

36:08 recap of what the pool what the pulled
36:11 

36:11 funds are really about if you were are
36:12 

36:12 new to this meeting and just kind of
36:14 

36:14 overall discussion and Julie's going to
36:16 

36:16 talk about version structures John I'll
36:18 

36:18 give an update on I infra and then Julie
36:21 

36:21 will come back in and talk about some
36:23 

36:23 engagement needs that are relevant to
36:25 

36:25 both pulled funds Next slide, Julie.
36:29 

36:29 So, real quickly, the overview, go to
36:31 

36:31 the next one.
36:35 

36:35 When it came down to what we're trying
36:37 

36:37 to do is we had a problem to solve.
36:39 

36:39 Developer designers divi design in
36:41 

36:41 certain software that is good for
36:43 

36:43 authoring models and information.
36:45 

36:45 Contractors and operators don't use
36:47 

36:47 those same the same tools or they're not
36:50 

36:50 necessarily able to understand those
36:52 

36:52 tools the same way. Um a great example
36:55 

36:55 is I uh the design software is very good
36:57 

36:57 at making very very intricate things but
36:60 

36:60 that's not necessarily always the same
37:02 

37:02 uh needs that people downstream need
37:05 

37:05 have when it comes to data. So there's
37:07 

37:07 interoperability interoperability issue
37:09 

37:09 when it came to presenting information
37:12 

37:12 flowing through because design software
37:16 

37:16 they're proprietary uh modeling viewing
37:18 

37:18 softwares are proprietary uh if it goes
37:21 

37:21 off the PDF and you're you're missing
37:23 

37:23 data and various things like that. So
37:24 

37:24 the bullet funds vision was to get
37:26 

37:26 consistent way to exchange information
37:29 

37:29 in a repeatable methodology. So really
37:33 

37:33 what what it came down to was we're
37:35 

37:35 handing off information. We need to know
37:37 

37:37 that it's structured in a similar way so
37:39 

37:39 that software developers can read that
37:40 

37:40 information no matter what the authoring
37:42 

37:42 software was. And that came down to the
37:44 

37:44 solution was develop implement adopt and
37:47 

37:47 govern and maintain national data
37:49 

37:49 standards. So this is all relative to um
37:54 

37:54 IFC development that was adopted in 2019
37:57 

37:57 by ASHTO administ administrative
37:59 

37:59 resolution AR19 where ASHTTO officially
38:02 

38:02 came through and said that IFC will be
38:04 

38:04 the official data schema for
38:07 

38:07 transportation projects moving forward.
38:09 

38:09 Next one, Julie.
38:12 

38:12 So, what is this what is this problem
38:14 

38:14 really coming in down to? It's like,
38:16 

38:16 like I said, design is creating
38:17 

38:17 information. That information is being
38:19 

38:19 passed on to multiple customers. It
38:21 

38:21 could be construction, it could be
38:22 

38:22 fabrication, um, and ultimately through
38:26 

38:26 construction and fabrication and going
38:27 

38:27 on to asset management to be able to
38:29 

38:29 figure out exactly what our assets are.
38:31 

38:31 So each one of those phases come through
38:34 

38:34 and you look on the right hand side
38:35 

38:35 there and federal highways kind of show
38:37 

38:37 this the the process of life cycle
38:39 

38:39 information where there's breakthroughs
38:42 

38:42 each time. So there's a drop of
38:43 

38:43 information. So if you're handing off
38:45 

38:45 from a design model to a PDF and then
38:48 

38:48 you're you're losing information, you're
38:49 

38:49 losing fidelity. And we want to get to
38:52 

38:52 the point where that information just
38:53 

38:53 flows
38:54 

38:54 u flows naturally throughout the system.
38:59 

38:59 And that's the point of this through
39:01 

39:01 these different uh technologies. You see
39:03 

39:03 in the middle there IFC IFC is just a
39:05 

39:05 data schema. And so what we need to do
39:09 

39:09 is configure exactly what it is that
39:12 

39:12 we're communicating through that data
39:14 

39:14 schema. IFC was developed for the
39:16 

39:16 vertical industry and the horizontal and
39:18 

39:18 vertical or we're all building things
39:20 

39:20 but there's very different necessities
39:23 

39:23 that are there when it comes to the
39:25 

39:25 horizontal uh transportation industry.
39:28 

39:28 Next one, Julie.
39:30 

39:30 >> So, it comes down to what's the need for
39:33 

39:33 consistent data? Well, an easiest
39:34 

39:34 example to say is almost everything in a
39:37 

39:37 transportation project goes down to
39:39 

39:39 alignments. All of our assets in
39:41 

39:41 construction, they're they're coming off
39:42 

39:42 alignments. When you're in operations,
39:43 

39:43 you're going off center lines. And so,
39:45 

39:45 there's a need to basically say that
39:47 

39:47 we're all communicating the same
39:48 

39:48 information. And so, that's the easiest
39:50 

39:50 example. So, we had to get together and
39:52 

39:52 kind of defi define each and every
39:54 

39:54 single aspect of a transportation
39:56 

39:56 project. And so starting off with
39:59 

39:59 alignments, that's just basics is some
40:01 

40:01 things we might call it one way in Iowa
40:04 

40:04 and it might be a different thing in
40:05 

40:05 Minnesota just to our neighbor to our
40:06 

40:06 north and around the country. We had to
40:08 

40:08 come up with a consistent naming
40:11 

40:11 consistent naming and data needs for
40:13 

40:13 every single aspect of these uh of these
40:18 

40:18 parts of the process. Next one Julie.
40:24 

40:24 So as you can see here approximately 28
40:26 

40:26 states around the country have been
40:28 

40:28 involved in either one of the poolled
40:30 

40:30 fund studies. Uh so BIM for bridges
40:32 

40:32 started a little bit earlier then BIM
40:34 

40:34 for infrastructure came in after the
40:35 

40:35 fact and bridge bridges and structures
40:37 

40:37 is now on phase two. Uh each of these
40:42 

40:42 states have contributed to being able to
40:44 

40:44 develop and have consistent data
40:45 

40:45 standards. uh we want to build out the
40:47 

40:47 foundation that the federal highways
40:49 

40:49 natural n national strategic roadmap
40:53 

40:53 developed for BIM for infrastructure
40:54 

40:54 really advancing
40:57 

40:57 BIM as an overall for the nation so we
40:59 

40:59 we can all do it collectively because if
41:01 

41:01 we pull our money together we can all do
41:04 

41:04 things in a consistent way and we're not
41:06 

41:06 doing something in Iowa something in
41:08 

41:08 Utah something in Pennsylvania we're all
41:10 

41:10 doing it together as a United States and
41:12 

41:12 that makes it a lot easier to give
41:14 

41:14 information to our customers downstream
41:16 

41:16 when we're working with fabrication um
41:19 

41:19 technology providers who are creating
41:20 

41:20 information for automated machine
41:21 

41:21 guidance or automated anything in the
41:24 

41:24 field when it comes down to various
41:25 

41:25 things. And so these pulled funds, they
41:28 

41:28 provide a a avenue for each of these
41:31 

41:31 states and any state really that is
41:34 

41:34 interested um to kind of share
41:38 

41:38 information, provide feedback on how we
41:40 

41:40 set these things up and really work
41:42 

41:42 through um the processes. And I believe
41:46 

41:46 in the chat we were going to be
41:47 

41:47 providing a road map that's been
41:49 

41:49 developed for each of the poolled funds.
41:51 

41:51 Um
41:53 

41:53 basically kind of deciding what each of
41:56 

41:56 the years uh for the each of the years
41:59 

41:59 for the poolled fund study will be
42:00 

42:00 developing each time. Next slide Julie.
42:06 

42:06 So the poolled funds are both very much
42:09 

42:09 um trying to develop very similar
42:13 

42:13 things. Bridges and structures is very
42:15 

42:15 focused on bridges and structures. It's
42:16 

42:16 being structural. There's a lot of
42:18 

42:18 things that are unique to that. And then
42:19 

42:19 brim for infrastructure is what we like
42:21 

42:21 to say is everything else. Uh so it's
42:24 

42:24 highways. So because roadway, drainage,
42:27 

42:27 utilities, traffic, survey, geotechnical
42:29 

42:29 assets, pretty much anything and
42:32 

42:32 everything that's not a bridging
42:33 

42:33 structure when it comes to that. So BIM
42:35 

42:35 for infrastructure has a big task to
42:37 

42:37 come on. But when it comes down to the
42:40 

42:40 the nitty-gritty of what the poolled
42:41 

42:41 funds are trying to establish, it's
42:43 

42:43 these national astro endorsed IDMs, ids
42:47 

42:47 data dictionaries. If you haven't heard
42:49 

42:49 those terms before, IDM is information
42:52 

42:52 delivery manual. Uh IDS is information
42:56 

42:56 delivery specification and data
42:58 

42:58 dictionary is spelled out. But each of
43:00 

43:00 those have respective u purposes. The
43:04 

43:04 IDM defines what goes into the data
43:06 

43:06 exchanges, what needs to be required.
43:08 

43:08 The defines how those things are. Data
43:10 

43:10 dictionary works in tandem with the IDM
43:12 

43:12 to kind of spell out what everything is
43:14 

43:14 and the IDs is a machine readable
43:16 

43:16 information that software developers
43:18 

43:18 will then use to be able to use to apply
43:20 

43:20 these specifications their software. So
43:21 

43:21 when they're building out what is being
43:23 

43:23 done, they can have consistent outcomes
43:26 

43:26 as we move from software to software. So
43:28 

43:28 it gets to be something I heard
43:30 

43:30 yesterday in a different beer exchange,
43:31 

43:31 data agnostic. Some people have said
43:32 

43:32 software agnostic, but really what we're
43:34 

43:34 looking at is data that moves seamlessly
43:38 

43:38 and fluently. Um,
43:41 

43:41 so the the two pool of funds have been
43:44 

43:44 very much working in tandem uh in the
43:46 

43:46 last recently trying to develop these
43:48 

43:48 things because there's certain things
43:49 

43:49 that were developed early on in version
43:51 

43:51 structures that were like for alignments
43:53 

43:53 for example that infrastructure is
43:55 

43:55 really in charge of. So there's a lot of
43:56 

43:56 coordination between them. And the last
43:60 

43:60 uh bullet there as well is industry
44:03 

44:03 engagement of industry stakeholders.
44:04 

44:04 That's very important. Uh bridge and
44:06 

44:06 structures were currently focusing on
44:08 

44:08 trying to get an establishing working
44:10 

44:10 relationship with fabricators because
44:12 

44:12 that is part of our our plan here for
44:15 

44:15 data exchanges in the second phase of
44:17 

44:17 vision structures. And that's important
44:20 

44:20 to be able to figure out exactly what it
44:22 

44:22 is our customers actually need and can
44:24 

44:24 use so we can effectively deliver
44:26 

44:26 information. um through throughout the
44:29 

44:29 life cycle. Next slide.
44:33 

44:33 So, I'll hand it over to Julie now to
44:35 

44:35 talk about version structures.
44:39 

44:39 >> Thanks very much, Thomas. All right, got
44:41 

44:41 my camera on and I think I am ready to
44:44 

44:44 go. So, yes, I will give a brief update
44:47 

44:47 on the BIM for Bridges and Structures
44:49 

44:49 Pool Fund and I know Jim Halber from
44:51 

44:51 Iowa DOT is on the line too and he is
44:53 

44:53 the study champion on the DOT side.
44:57 

44:57 Um, perhaps many of you have seen some
44:59 

44:59 presentations. I won't get into a lot of
45:01 

45:01 details, but I want to at least provide
45:03 

45:03 a high level overview and an update on a
45:05 

45:05 few key elements of the of this project.
45:08 

45:08 So, we are currently in that uh the
45:10 

45:10 phase two and I'll explain what that
45:11 

45:11 means in a moment, but uh we have 24
45:13 

45:13 states participating which is fantastic
45:15 

45:15 about half the country. There's always
45:17 

45:17 room for more but uh what we're trying
45:20 

45:20 to do the problem to solve with a vision
45:22 

45:22 and the solution is exactly what Thomas
45:24 

45:24 mentioned earlier. um that applies to
45:26 

45:26 both poolled funds. So, same exact um
45:29 

45:29 purpose um but focused on bridges
45:31 

45:31 obviously. Uh we do have a website there
45:34 

45:34 that's listed if you haven't visited it.
45:36 

45:36 Feel free to take a look for more
45:38 

45:38 information.
45:40 

45:40 So, there's two poolled fund studies.
45:42 

45:42 One has concluded. So, the one that's uh
45:45 

45:45 in the upper left there, TPF 5372 was
45:48 

45:48 the phase one pulled fund that took
45:51 

45:51 place between 2018 and 2024.
45:54 

45:54 And this was the project where we
45:56 

45:56 developed the initial set of standards
45:59 

45:59 for exchanging 3D bridge models. And we
46:01 

46:01 specifically focused on the design to
46:03 

46:03 construction data exchange. And the
46:06 

46:06 purpose of this data exchange was to
46:08 

46:08 enable contractors to prepare their bids
46:11 

46:11 and execute construction in a design bid
46:14 

46:14 build procurement type environment. uh
46:16 

46:16 when I talk about a data exchange uh I'm
46:18 

46:18 talking about one point in time one
46:20 

46:20 handoff of information in the life cycle
46:23 

46:23 of a bridge for example uh to talk about
46:27 

46:27 data exchanges we uh we have a process
46:30 

46:30 map which is shown in the lower right
46:32 

46:32 just to give you a sense that this is
46:33 

46:33 this is a tool basically to look at the
46:36 

46:36 life cycle of a bridge and um the pool
46:40 

46:40 fund members selected that design to
46:41 

46:41 construction exchange which is one of 19
46:44 

46:44 exchanges identified in the process map
46:46 

46:46 as the as the first priority. Now we are
46:49 

46:49 in the phase 2 study TPF 5523.
46:53 

46:53 That work is ongoing um from we started
46:55 

46:55 in early 2024 expected to continue
46:58 

46:58 through 2028.
47:00 

47:00 And the goal of this phase 2 effort is
47:03 

47:03 to both advance the initial the initial
47:05 

47:05 standards and also to create additional
47:09 

47:09 data exchange standards. And the focus
47:12 

47:12 um selected by the pool plan members in
47:14 

47:14 this case is related to fabrication
47:16 

47:16 details and asbuilt conditions. So the
47:19 

47:19 box in the little graphic there is is is
47:22 

47:22 identifying the additional date
47:23 

47:23 exchanges that will be our our focus and
47:26 

47:26 our they are our focus for phase two.
47:31 

47:31 I wanted to briefly mention the phase
47:33 

47:33 one outcomes uh because that does
47:35 

47:35 pertain to some of the work that we're
47:36 

47:36 continuing to do right now. Um Thomas
47:40 

47:40 mentioned these three types of work
47:42 

47:42 products IDM, ids and data dictionary.
47:45 

47:45 Uh so we did produce those for that one
47:47 

47:47 data exchange in phase 1. The IDM is an
47:50 

47:50 actual manual. It's a PDF. It was
47:53 

47:53 published by ASHTTO in January of 2023.
47:56 

47:56 It is available on the ASHTTO store
47:59 

47:59 website for purchase a PDF format. Um so
48:03 

48:03 if you haven't already heard of that, it
48:05 

48:05 might be something of interest. and and
48:07 

48:07 these are critical tools to be um tested
48:11 

48:11 in industry and on the next slide I'll
48:14 

48:14 be talking about how these items how
48:16 

48:16 these work products have been used and
48:18 

48:18 tested on pilot projects.
48:23 

48:23 So in 2025 there were three pilot
48:26 

48:26 projects done by uh these these states
48:29 

48:29 here PENDOT and Iowa DOT. These projects
48:32 

48:32 were funded by FHWA's uh ADCMS grant
48:36 

48:36 program and these projects utilized
48:39 

48:39 those national standards that were
48:41 

48:41 developed by the phase one BIM for
48:43 

48:43 Bridges Pulled fund. Um, so it was great
48:45 

48:45 to see those products in action and they
48:49 

48:49 basically took the uh the data standards
48:52 

48:52 and and chose the modeling software of
48:54 

48:54 their of their choice and worked with
48:56 

48:56 the vendors to make sure those data
48:59 

48:59 standards were incorporated approp
49:01 

49:01 appropriately so they could get an IFC
49:02 

49:02 export out of that software and then
49:04 

49:04 that IFC model could be imported to
49:06 

49:06 other tools. Uh in the case of that
49:09 

49:09 middle project, the SR6 uh PENDOT
49:11 

49:11 project, the IFC model was actually the
49:14 

49:14 legal deliverable.
49:16 

49:16 Um and our the BIM for Bridges poolled
49:19 

49:19 fund team was was involved um with some
49:22 

49:22 coordination and some advising, but we
49:25 

49:25 also got some great feedback which I'll
49:27 

49:27 talk about in a moment. But it is really
49:29 

49:29 a significant thing to note that this
49:32 

49:32 IFC model as a legal deliverable was
49:34 

49:34 really the first of its kind in the
49:37 

49:37 United States. this had not been done
49:38 

49:38 before. So kudos to the project team and
49:41 

49:41 to PennDOT for making that happen and uh
49:44 

49:44 we look forward to more pilot projects
49:46 

49:46 in the future. I also wanted to give um
49:51 

49:51 an example of how this actually uh
49:54 

49:54 works. Um, so this is um
49:60 

49:60 this was a a screenshot and courtesy of
50:03 

50:03 Joe Brener of Michael Baker. And this is
50:05 

50:05 from that SR6 pendot project. And this
50:08 

50:08 data that we're seeing on the screen,
50:10 

50:10 this IFC model was produced from a
50:12 

50:12 non-bently tool called Open Brim. And
50:15 

50:15 then the IFC model was imported into a
50:17 

50:17 Bentley tool called Synchro. And it
50:20 

50:20 preserved the data, the properties, and
50:22 

50:22 all the attributes.
50:24 

50:24 And that's that's the significance of
50:26 

50:26 this. Likewise, the same IFC model was
50:31 

50:31 imported to this Ubim tool. This is an
50:34 

50:34 IFC viewer. So again, it's not just
50:37 

50:37 about having a 3D model that looks
50:39 

50:39 correct graphically, but rather it's
50:41 

50:41 maintaining the the attributes and the
50:42 

50:42 properties structured in the correct
50:44 

50:44 format. So that's the the significance
50:47 

50:47 of having these tools. Um, and I just
50:50 

50:50 wanted to share that those brief
50:51 

50:51 examples. I know there's there's been
50:53 

50:53 presentations on these pilot projects in
50:55 

50:55 various venues. So, if you haven't seen
50:57 

50:57 them yet, uh you can look for them
50:59 

50:59 online. I know the open BIM
51:01 

51:01 transportation summit from November of
51:04 

51:04 2025 has a recorded presentation
51:07 

51:07 available on the BuildingSmart USA
51:10 

51:10 website. Um I'm sure we can get that
51:12 

51:12 link in the chat, but um that might be
51:15 

51:15 another place to go if you would like
51:17 

51:17 more information about these pilot
51:19 

51:19 projects.
51:20 

51:20 And why is this so significant for the
51:22 

51:22 BIM for Bridges and Structures study?
51:25 

51:25 Well, um, one of our tasks, um, that has
51:28 

51:28 been a key focus in the past year was
51:31 

51:31 using the feedback that we got from the
51:33 

51:33 pilot project teams in order to refine
51:36 

51:36 and update the standards from the phase
51:38 

51:38 one effort. And this is critical because
51:40 

51:40 we were producing things that hadn't
51:42 

51:42 been done before. You know, unchartered
51:44 

51:44 territory, a brand new path, if you
51:45 

51:45 will. That's why I included this little
51:47 

51:47 graphic in the upper left. We're going
51:49 

51:49 down a road that no one has gone down
51:51 

51:51 before in the US and for transportation
51:54 

51:54 and even doing this at the national
51:55 

51:55 level is somewhat unique even
51:57 

51:57 internationally. So we're taking that
52:00 

52:00 feedback from the pilot projects teams
52:02 

52:02 and updating um those standards and that
52:05 

52:05 work has been recently completed and
52:07 

52:07 this is also critical because those
52:09 

52:09 updated data standards serve as a
52:11 

52:11 foundation for the the next set of data
52:14 

52:14 standards that we were we are about to
52:16 

52:16 embark on.
52:18 

52:18 Um so other tasks that we are doing in
52:20 

52:20 phase two just at a glance um a couple
52:23 

52:23 of tasks that have been completed
52:24 

52:24 already uh early on in the phase 2
52:27 

52:27 efforts we established our methodology.
52:29 

52:29 So we took what we did in phase one and
52:31 

52:31 really documented the process for
52:33 

52:33 developing the standards. It's not a
52:35 

52:35 straightforward linear process. There's
52:37 

52:37 a lot of iteration. So we have that
52:39 

52:39 documented for our team to follow and
52:41 

52:41 also to communicate to the pulled fund
52:43 

52:43 sponsors and others what is involved
52:45 

52:45 with the work that we're doing. We also
52:48 

52:48 uh worked with the pulled fund members
52:50 

52:50 to identify those priority data
52:52 

52:52 exchanges that I already mentioned the
52:54 

52:54 fabrication detail exchange and the um
52:57 

52:57 exchanges related to asbuilts.
53:01 

53:01 uh and we are on on the brink of
53:03 

53:03 starting development of the new
53:05 

53:05 standards and we will be um working with
53:10 

53:10 stakeholders and we'll be talking about
53:11 

53:11 that in in a little bit um what that
53:14 

53:14 what that will look like and we want to
53:16 

53:16 test the draft standards with software
53:18 

53:18 developers and then have this um
53:20 

53:20 collaborative process to really update
53:22 

53:22 those technical work products and then
53:25 

53:25 get them to a point where we can share
53:26 

53:26 them with industry share them with state
53:28 

53:28 DOS and other stakeholders so that they
53:30 

53:30 and test them out um and provide
53:33 

53:33 additional feedback and then ultimately
53:35 

53:35 publish these standards. What publishing
53:38 

53:38 means or endorsing them um is something
53:41 

53:41 that's being worked out. That's a
53:42 

53:42 governance question. Uh that'll be um
53:46 

53:46 something to to determine at the
53:48 

53:48 national level through the ASHTO uh
53:51 

53:51 joint subcommittee on data
53:53 

53:53 standardization and groups like that.
53:56 

53:56 But again, I wanted to highlight that
53:58 

53:58 these two steps here involve
53:60 

53:60 stakeholders and that's what we'll be
54:01 

54:01 talking about more in a few minutes and
54:04 

54:04 how the DDSG can be involved with these
54:06 

54:06 test with these steps um of providing
54:10 

54:10 input on our work and receiving the
54:14 

54:14 draft standards and putting them to
54:15 

54:15 putting them to use.
54:18 

54:18 So touch on that in a few more minutes
54:20 

54:20 when we talk about collaboration a
54:22 

54:22 little bit more. But before I hand it
54:24 

54:24 off to John and the B infrastructure
54:27 

54:27 team, I wanted to share one more thing
54:29 

54:29 which is exciting. Uh like I mentioned,
54:32 

54:32 we are hopeful to see additional pilot
54:34 

54:34 projects be done by other state DOS. Uh
54:39 

54:39 hopefully you know this year and in the
54:40 

54:40 next couple of years where the teams
54:43 

54:43 would use the open BIM process using the
54:46 

54:46 um data standards produced by the BIM
54:49 

54:49 for Bridges pool fund. So we are looking
54:51 

54:51 for more states and there is um
54:55 

54:55 something here ex exciting there's a
54:57 

54:57 reward for states who want to
54:59 

54:59 participate and and do these pilot
55:01 

55:01 projects there is support available so
55:04 

55:04 working with Jim Halber at Iowa DOT
55:06 

55:06 there's a plan in place to support
55:09 

55:09 states that want to do this uh we will
55:11 

55:11 provide um some technical support in the
55:14 

55:14 planning process and throughout the the
55:17 

55:17 the efforts that the state is doing you
55:19 

55:19 know the pilot pilots would be led by
55:21 

55:21 the states. This is just sort of
55:22 

55:22 advisory support from the poolled fund
55:25 

55:25 technical team because that will be
55:27 

55:27 critical. Also, we recognize that there
55:30 

55:30 needs to be continued f uh coordination
55:32 

55:32 with software vendors which would which
55:35 

55:35 uh the product whatever product the
55:36 

55:36 state wants to use. Um perhaps it would
55:39 

55:39 be one of the ones listed on the side,
55:41 

55:41 but it could be it could be any software
55:44 

55:44 um or technology provider and our team
55:47 

55:47 would be uh assisting with facilitating
55:49 

55:49 those coordination meetings which are
55:51 

55:51 critical for the success of a pilot
55:53 

55:53 project. And then our team would also
55:55 

55:55 want to document the lessons learned,
55:57 

55:57 get feedback so we can continue to
55:59 

55:59 improve the the work that we're doing to
56:01 

56:01 define these um national standards. Um
56:05 

56:05 the idea or the the recommendation would
56:08 

56:08 be for states that are interested in
56:09 

56:09 getting this type of support uh that
56:12 

56:12 they would contribute financially and
56:14 

56:14 that's being handled by Iowa DOT. Um the
56:18 

56:18 ef this effort would be rolled into the
56:19 

56:19 current BIM for Bridges poolled fund.
56:22 

56:22 It's important to note that this
56:24 

56:24 opportunity is not limited just to
56:26 

56:26 current states that are participating in
56:29 

56:29 the BIM for Bridges pool fund but other
56:31 

56:31 states that may not be in the pool fund
56:32 

56:32 are also welcome. um to participate. If
56:36 

56:36 you are interested, please uh contact
56:39 

56:39 Jim Hubber and his email address is
56:42 

56:42 noted there. So that's that's the last
56:44 

56:44 item I had. Um
56:46 

56:46 >> Julie, can I add a few more things on
56:48 

56:48 that?
56:48 

56:48 >> Yes.
56:49 

56:49 >> So this is an effort that is needed. You
56:52 

56:52 know, when completing those first pilot
56:54 

56:54 projects, um the research team for Ben
56:58 

56:58 for Bridge provided a lot of support and
56:60 

56:60 communication with the software vendors.
57:02 

57:02 Now, that was additional resources. You
57:04 

57:04 know, some of it they did on their their
57:06 

57:06 their dime, but they did use some BIM
57:08 

57:08 for Bridge ref uh resources for that
57:11 

57:11 effort. But this really needs to be a
57:13 

57:13 coordinated effort. Um we can't have 50
57:15 

57:15 states going to Bentley, Audreel, and
57:18 

57:18 other software vendors asking for
57:21 

57:21 certain items. We really need, you know,
57:23 

57:23 we're trying to develop a national
57:24 

57:24 standard which is very different than
57:26 

57:26 what was done in Europe. you know their
57:28 

57:28 their standards are very or their
57:30 

57:30 delivery is very project specific and in
57:34 

57:34 creating a national standard we really
57:35 

57:35 need to speak with that one voice and I
57:37 

57:37 really want to stress this is open you
57:39 

57:39 don't have to be in the poolled funds in
57:41 

57:41 order to participate um if you're a
57:43 

57:43 state that didn't have the resources at
57:45 

57:45 the time to participate in ben for
57:47 

57:47 bridge bin for infra um you can still
57:50 

57:50 participate in this effort and try to
57:52 

57:52 pilot and use IFC as a deliverable
57:55 

57:55 product um please just email me the
57:57 

57:57 emails, send me a chat, whatever you
57:59 

57:59 need. Um, there will be an email
58:01 

58:01 probably coming out later this week with
58:02 

58:02 the pool. I'll be sending another mass
58:05 

58:05 email to the BIM for Bridge BIM for
58:07 

58:07 infrastructure champions. Um, trying to
58:08 

58:08 get see how many states are interested
58:10 

58:10 in actually piling in this stuff. Um,
58:12 

58:12 I'm fairly optimistic based on BIM week.
58:14 

58:14 There was roughly 8 to 10 states that
58:17 

58:17 indicated interest. Um, I hope that's
58:18 

58:18 still the case. Um, like I said, if you
58:20 

58:20 have any questions or concerns, please
58:22 

58:22 reach out to me. Thanks, Julie.
58:25 

58:25 >> No problem. And uh hey Julie Jim Jim
58:28 

58:28 just for clarity this is you you talked
58:30 

58:30 about this on on Monday too so people
58:33 

58:33 would know it's the same program that
58:36 

58:36 you presented
58:37 

58:37 >> on Monday. So
58:39 

58:39 >> Oh yeah. But this is a much this is a
58:40 

58:40 much better slide.
58:42 

58:42 >> Yeah.
58:44 

58:44 Well and it's you know it's good to
58:47 

58:47 repeat because it takes a while for
58:49 

58:49 things to get through. So and we've got
58:52 

58:52 some different folks here. So this is
58:53 

58:53 great and just wanted to point that out.
58:56 

58:56 >> Yep. And you know creating and utilizing
58:58 

58:58 it you know the benefit sometimes I get
59:00 

59:00 asked well you know what are the full
59:03 

59:03 benefits? Well the main benefit is the
59:04 

59:04 DOT then owns their data as you saw that
59:06 

59:06 interoperability to different software
59:08 

59:08 viewers. It allows you to own your data
59:12 

59:12 as an owner. So you can keep that file
59:14 

59:14 you save it you know part of your bridge
59:15 

59:15 inspection software. You guys I'm sure
59:18 

59:18 most states have a PDF copy that you
59:20 

59:20 keep as part of that. Well, this ensures
59:22 

59:22 that you'll be able to keep that model
59:23 

59:23 for the life of that structure. Thanks,
59:26 

59:26 Julie.
59:27 

59:27 >> Yeah, no problem. So, I will hand it off
59:30 

59:30 now to John and I'll come back later for
59:33 

59:33 the the last section.
59:36 

59:36 >> Thanks, Julie. Thanks, Jim. Thanks,
59:38 

59:38 Thomas. Um, thanks for having us. Um, to
59:41 

59:41 kind of go over where we're trying to go
59:42 

59:42 with industry engagement kind of set the
59:45 

59:45 table. Um, I'm managing the the um
59:49 

59:49 co-manager of the uh pen infrastructure
59:51 

59:51 pool fund. Matthew Miller is the TPS
59:54 

59:54 studying champion. As Thomas noted, him
59:56 

59:56 and and Kent Nicholson at DOT are also
59:60 

59:60 assisting. Um, so really just to get
60:04 

60:04 into it, um, I posted in the chat, um, a
60:07 

60:07 link to the knowledge platform. Um, one
60:09 

60:09 of the big goals that we had early on,
60:12 

60:12 um, was to really set a foundation to
60:15 

60:15 allow states to move forward on their
60:18 

60:18 BIM for infrastructure journey, um,
60:21 

60:21 following along the national strategic
60:23 

60:23 road map. And so there are a lot of
60:25 

60:25 deliverables we released in the first
60:26 

60:26 year. Um, and those are uh, pulled into
60:31 

60:31 this knowledge platform um, that exist
60:33 

60:33 on the website that I put in the in the
60:35 

60:35 chat. really the intent is for you to be
60:37 

60:37 able to ask it questions. You have to
60:39 

60:39 it's still being trained um so that they
60:42 

60:42 can they you can find the the pieces and
60:45 

60:45 the parts and it should link back to to
60:47 

60:47 the original products um and really help
60:51 

60:51 really navigate that. There's there's a
60:54 

60:54 a white paper in there on u IC and its
60:56 

60:56 role in BIM. Um there is a white there's
60:59 

60:59 a discussion on how to start a a BIM
61:02 

61:02 piloting process really looking at high
61:04 

61:04 level but also bringing in some examples
61:06 

61:06 of what states have done. I think you'll
61:08 

61:08 see Penn dot and you do and several
61:10 

61:10 other states involved in in in those uh
61:13 

61:13 documents but those kind of roll up. Uh
61:16 

61:16 there's an exercise that I presented um
61:19 

61:19 uh during Ben week and to just kind of
61:22 

61:22 go through what what you can do with
61:24 

61:24 that. It took me a few rounds to get how
61:26 

61:26 do I get started as a state right? So
61:28 

61:28 you can ask it those questions. Um we're
61:30 

61:30 trying to add to that um by um probably
61:34 

61:34 by this summer uh releasing uh videos
61:38 

61:38 and flyers that kind of build out a a a
61:41 

61:41 dynamic web interface that could also be
61:44 

61:44 um the flyers could be PDFed for you
61:46 

61:46 know basically um lead behinds and and
61:49 

61:49 one page one pagers. Uh but th the
61:52 

61:52 intent of those is to work together to
61:54 

61:54 kind of help you know with these
61:55 

61:55 different audiences the executive the
61:57 

61:57 the actual BIM implementers at a at a
61:60 

61:60 agency and then the practitioners so
62:02 

62:02 that they know how their role fits into
62:04 

62:04 a BIM process u and really kind of
62:06 

62:06 setting the table based off the the
62:09 

62:09 poolled funds perspective what is BIM in
62:11 

62:11 a digital model and how does it benefit
62:13 

62:13 you um so that's really a lot of what's
62:16 

62:16 in that. Um so um we really set the
62:20 

62:20 foundation but we also knew that we
62:21 

62:21 needed to go forward and start to build
62:23 

62:23 off of what the BIM for Bridges and
62:25 

62:25 Structures has done um with establishing
62:28 

62:28 u data standards uh built around the IC
62:31 

62:31 schema.
62:33 

62:33 So in in in year two we kind of pivoted.
62:37 

62:37 Um in year one we had a overall workflow
62:41 

62:41 uh graphic um that I'll drop in the link
62:43 

62:43 in a little bit. Um, but this is a a
62:47 

62:47 focused in view on that. We took that
62:49 

62:49 bigger workflow graphic. I think it had
62:51 

62:51 40ome exchanges in it. Um, cuz we're
62:54 

62:54 talking about all these uh different
62:56 

62:56 disciplines and functional units, you
62:58 

62:58 know, that you see on the left. Uh,
62:59 

62:59 roadway, survey, earthwork, drainage,
63:02 

63:02 utility, geotech, and what we term
63:04 

63:04 traffic. Um, but, uh, signals, lighting,
63:08 

63:08 traffic systems. um and really focusing
63:11 

63:11 on we did a few workflow uh infographics
63:14 

63:14 and and process maps uh for
63:17 

63:17 reconstruction or reservicing, but we
63:19 

63:19 focused in on full reconstruction kind
63:21 

63:21 of thinking about that rural to urban
63:24 

63:24 state route and really uh what I like to
63:27 

63:27 think of being in Michigan. It's all
63:29 

63:29 those routes that get you to and from
63:32 

63:32 all those smaller tourist uh towns uh
63:35 

63:35 M22 being one of them. takes you along
63:37 

63:37 Lake Michigan. You're going from that
63:39 

63:39 rural route into that downtown. Really
63:42 

63:42 trying to capture that project that a
63:43 

63:43 lot of states work on say 80% of the
63:46 

63:46 time, not necessarily 80% of your
63:48 

63:48 funding, but 80% of your work. Um, so
63:51 

63:51 these maps can be used to assess the
63:53 

63:53 project phases, the activities, the
63:55 

63:55 actors, and exchange models. So, a lot
63:57 

63:57 of this will come out in in further
63:59 

63:59 detail when you start diving into some
64:01 

64:01 of the samples that we're wanting to
64:03 

64:03 engage with industry on and get into
64:05 

64:05 more technical working groups as Julie
64:07 

64:07 already alluded to. Just trying to walk
64:09 

64:09 you down the path of how we got to where
64:11 

64:11 we are. So, we had the the states vote
64:14 

64:14 on these exchanges. We kind of grouped
64:16 

64:16 them into like I can't remember there's
64:18 

64:18 like 10 exchanges um and had them vote
64:20 

64:20 on which one we should focus on.
64:22 

64:22 Surprise, surprise, design construction
64:24 

64:24 rose to the top mainly because you need
64:27 

64:27 a bridge and a road, right? Um they kind
64:29 

64:29 of got to, you know, work together in
64:31 

64:31 some fashion. Uh there's this
64:33 

64:33 overwhelming need to understand how we
64:35 

64:35 can leverage alignments and these linear
64:37 

64:37 components that that go into a bridge
64:39 

64:39 and make sure we're on the same page. So
64:41 

64:41 really, this is that design to to
64:43 

64:43 construction or to the letting um
64:46 

64:46 advertisement, right? That's the event
64:48 

64:48 and it kind of on the design side, this
64:50 

64:50 is where you're federating all your
64:52 

64:52 different discipline models into a final
64:55 

64:55 contract uh model um to leverage for
64:58 

64:58 takeoffs and estimates and automated
65:00 

65:00 machine guidance. There's some other use
65:02 

65:02 cases for that model, but we didn't
65:05 

65:05 really focus on those other use cases
65:07 

65:07 because it would been overwhelming. The
65:09 

65:09 goal was to really set the table for a
65:11 

65:11 lot of the disciplines and how they can
65:13 

65:13 interact and the information we need in
65:16 

65:16 between these different types of objects
65:18 

65:18 and elements. Um so we can continue to
65:20 

65:20 build on that as we go forward.
65:23 

65:23 Um the other uh exchange that kind of
65:25 

65:25 rose to the top is digital asbuilts. Um
65:28 

65:28 part of this is really trying to look at
65:30 

65:30 this from both sides of the uh
65:33 

65:33 construction process, right? What goes
65:35 

65:35 into it and what comes out of it. how
65:37 

65:37 can you bring this information back into
65:38 

65:38 your asset inventories, your operations
65:41 

65:41 and maintenance and future strategic
65:43 

65:43 planning, etc. Um, so really this starts
65:47 

65:47 to consume some of that information
65:48 

65:48 that's can generate in construction. One
65:51 

65:51 of the things we talk about a lot is is
65:53 

65:53 this a static thing and then there's
65:55 

65:55 other things that go into an asset
65:56 

65:56 inventory um or is it the same thing and
65:60 

65:60 where is that information coming from?
66:02 

66:02 What can we pull from the design
66:03 

66:03 information? what gets re regenerated
66:06 

66:06 out in the construction. We want to
66:07 

66:07 understand um the different properties
66:09 

66:09 and property sets in the data. So
66:11 

66:11 there's a lot of discussions around that
66:13 

66:13 when you get into these subgroups and
66:15 

66:15 kind of a representative of how that
66:16 

66:16 tends to look um is in is on the the
66:20 

66:20 next slide. Um really that information
66:23 

66:23 how it builds through the the life cycle
66:26 

66:26 right at the planning surveying level.
66:28 

66:28 You're pulling information out of the
66:30 

66:30 asset inventory. you know you have an
66:32 

66:32 object or you know have you have a need
66:34 

66:34 to create an object, right? So you kind
66:36 

66:36 of know where it is in your inventory
66:38 

66:38 along a road. It has a project number.
66:40 

66:40 It has an ID. Um you know what type of
66:43 

66:43 light you want to, you know, put in
66:45 

66:45 there, illuminire. Um whether it's a
66:47 

66:47 sign, you know, mounted on a signal or
66:49 

66:49 it's roadway lighting or it's
66:50 

66:50 interchange tower lighting, etc. Then
66:52 

66:52 you get into design, you start to
66:54 

66:54 understand what it's the light
66:56 

66:56 distribution needs to be and where
66:58 

66:58 particular luminers are going to need to
67:00 

67:00 be. Um, and those types of things and
67:03 

67:03 you confirm that what you're doing is is
67:06 

67:06 what you originally needed to do. Um,
67:09 

67:09 then you get into construction and you
67:10 

67:10 confirm locations. You identify the
67:14 

67:14 manufacturer. You document the
67:16 

67:16 collection method making sure it's
67:18 

67:18 certified to what it was intended to be
67:20 

67:20 and follows your standards. Then you
67:23 

67:23 pass that information into the asset
67:25 

67:25 system. It starts to inherit some age
67:27 

67:27 and condition information,
67:29 

67:29 certification, validation informations
67:31 

67:31 there, etc. So I just this is not
67:33 

67:33 everything, right? This is just kind of
67:35 

67:35 a high level helps people kind of um
67:38 

67:38 make make sense about what we're talking
67:40 

67:40 about with all these process maps. Um
67:42 

67:42 cuz a lot of that discussion can be
67:44 

67:44 confusing for the average person that
67:46 

67:46 doesn't have to get into the weeds all
67:47 

67:47 the time.
67:50 

67:50 So where are we at and where we're
67:51 

67:51 going? Um we're working on our IDM and
67:55 

67:55 IDS. We're currently um the tag uh the
67:58 

67:58 pool fund is actually reviewing um the
68:01 

68:01 draft IDM for design to construction. Um
68:04 

68:04 we're hoping to have uh that ready uh
68:07 

68:07 this spring summer for more engagement
68:09 

68:09 as well as building out the digital
68:12 

68:12 asbuilt um information delivery manual
68:15 

68:15 um as we start to look at mapping that
68:18 

68:18 into um the IC schema and developing the
68:22 

68:22 IDS um going into into next year. Um but
68:27 

68:27 really right now that what is the
68:30 

68:30 information required and how is it
68:32 

68:32 structured that's the thing that will be
68:34 

68:34 coming up probably you know late spring
68:37 

68:37 um early summer uh for more engagement
68:39 

68:39 from industry as a whole. Um and also
68:43 

68:43 going back to the the plug that was
68:45 

68:45 noted on pilot projects, we have uh set
68:49 

68:49 aside a support with our project uh
68:52 

68:52 already to kind of support some pilot
68:55 

68:55 projects in this regard um you know as
68:58 

68:58 as we move that forward into next year
69:00 

69:00 looking at into like 2027ish
69:03 

69:03 um work. So, that's kind of a high level
69:07 

69:07 um of where we're at with with these
69:09 

69:09 design to construction and digital
69:10 

69:10 asbuilts. We started with design to
69:12 

69:12 construction and now we're we've added
69:15 

69:15 in and we got the the information
69:17 

69:17 requirements kind of figured out for
69:18 

69:18 digital asbuilts and now we're trying to
69:20 

69:20 uh we'll be starting to map those into
69:22 

69:22 an information delivery manual um after
69:25 

69:25 we get done with the design to
69:26 

69:26 construction information delivery
69:27 

69:27 manual. Um we tried to do these at one
69:29 

69:29 point um when we started out a couple
69:32 

69:32 years ago did design and construction
69:33 

69:33 and digitalized
69:36 

69:36 that led to a lot of questions and a lot
69:38 

69:38 of um back and forth and and and really
69:41 

69:41 took away uh some of the focus. So we
69:43 

69:43 had to focus in on one and then then
69:46 

69:46 come back to the other. Um
69:49 

69:49 um building off of what Julie said um
69:51 

69:51 just kind of looking more into our
69:54 

69:54 information delivery manual for design
69:56 

69:56 to construction. This is currently where
69:58 

69:58 we are. Uh we've broken these things
69:60 

69:60 into these different groupings. Um on
70:03 

70:03 the left you got the roadway geometry
70:05 

70:05 and features that's been reviewed by by
70:07 

70:07 the pulled fund. We're working on
70:09 

70:09 addressing those comments as we continue
70:11 

70:11 to extend the the information and
70:13 

70:13 delivery manual. Um we recently
70:16 

70:16 submitted the survey and earthwork um
70:19 

70:19 extension on the IDM. Um, we're working
70:21 

70:21 on the utilities and drainage and and
70:24 

70:24 then the traffic and geotechnical. So,
70:27 

70:27 our goal is to have all these reviewed
70:29 

70:29 by the end of February and then address
70:32 

70:32 the comments and in in March or early
70:35 

70:35 spring, start to get that out to
70:37 

70:37 industry for more input.
70:40 

70:40 With that, I'll turn it over to Julie. I
70:42 

70:42 think just kind of this kind of builds
70:44 

70:44 on we both have this shared need. We've
70:46 

70:46 talked about a lot of this at BMW week
70:49 

70:49 and last year even on how we really need
70:51 

70:51 to engage with industry. We're going to
70:52 

70:52 be talking to a lot of the same
70:54 

70:54 partners, but some of them may be
70:55 

70:55 different, but we need to really
70:56 

70:56 collaborate um and and work together so
70:59 

70:59 we're not, you know, as I think Roger
71:01 

71:01 said at the beginning, taking up more of
71:03 

71:03 everybody's precious time. So, thank
71:05 

71:05 you.
71:07 

71:07 >> All right,
71:07 

71:07 >> John. John, um just could you
71:10 

71:10 potentially either you or or Julia um
71:14 

71:14 just briefly describe what BIM is for
71:17 

71:17 those you know online that may not be
71:21 

71:21 familiar with with that uh aspect.
71:25 

71:25 >> We think uh BIM week kind of started
71:27 

71:27 what two three years ago. I think the
71:29 

71:29 first one technically I think was when
71:31 

71:31 our our pulled fund was getting started
71:33 

71:33 um in in March I believe it was kind of
71:35 

71:35 a mini pull together but part of it was
71:38 

71:38 trying to align what the pulled funds
71:40 

71:40 were doing but there's a lot of other
71:41 

71:41 things going on with some of the Ashtto
71:42 

71:42 committees and some other groups so it
71:44 

71:44 was to make sure that what we're doing
71:47 

71:47 uh aligned and then it evolved over the
71:49 

71:49 years and I guess this last year we had
71:52 

71:52 we worked with building smart uh USA um
71:56 

71:56 with their transportation committee um
71:58 

71:58 to kind of use that to align with their
72:00 

72:00 their yearly uh engagement midweek and
72:03 

72:03 and we had our our poolled fund meetings
72:06 

72:06 earlier in the week and we gradually
72:08 

72:08 worked towards you know on Fridays we
72:10 

72:10 typically end with a combined pulled
72:13 

72:13 fund session to make sure we're aligned
72:15 

72:15 on okay what do we need to do this year
72:17 

72:17 together and and what what did we miss
72:20 

72:20 last year to make sure that we pull that
72:21 

72:21 forward so I don't know if that if that
72:23 

72:23 helps get anything to add Julie
72:26 

72:26 >> sure yeah I can just elaborate a little
72:27 

72:27 it that um you know since both poolled
72:30 

72:30 funds started and bridge has been at
72:32 

72:32 this for several years now we really
72:34 

72:34 have one in-person meeting per year
72:37 

72:37 between the team and the poolled fund
72:39 

72:39 members since everybody's scattered
72:41 

72:41 across the country so we would generally
72:43 

72:43 get together for one to two days to have
72:45 

72:45 meetings to talk about the project and
72:48 

72:48 and working meetings really so um
72:51 

72:51 infrastructure has something similar so
72:53 

72:53 BIM week also combined those um specific
72:57 

72:57 specific project meetings, the business
72:58 

72:58 meetings in the same week and then at
73:01 

73:01 tacked on some additional um joint
73:04 

73:04 meetings as well as an open um
73:07 

73:07 opportunity through um this past year in
73:09 

73:09 November where the the summit is more of
73:12 

73:12 a conference open to everybody. Anyone
73:14 

73:14 could um register for that whereas the
73:17 

73:17 business meetings are are closed. Those
73:19 

73:19 are specific to the uh the poolled fund
73:22 

73:22 u members essentially. So that's it's
73:25 

73:25 just
73:27 

73:27 a a couple of meetings grouped together
73:29 

73:29 in one week since a lot there's a lot of
73:31 

73:31 overlap and everybody can be in the same
73:32 

73:32 place the same time
73:37 

73:37 >> you
73:39 

73:39 >> okay anything else Matt are ready to
73:41 

73:41 continue
73:43 

73:43 >> yeah please do
73:44 

73:44 >> all right uh so to close um to wrap up
73:47 

73:47 the the session here on the pulled funds
73:49 

73:49 I'll be talking a little bit about our
73:52 

73:52 vision for um engagement needs relative
73:55 

73:55 to the digital delivery stakeholder
73:57 

73:57 group.
74:01 

74:01 So why why would we need to do this?
74:05 

74:05 Well, the poolled fund work products
74:06 

74:06 pertain to data needs of many different
74:10 

74:10 stakeholders and it's not feasible in
74:13 

74:13 our, you know, current team of
74:15 

74:15 consultants plus our DOT sponsors to
74:19 

74:19 capture all that information and
74:21 

74:21 knowledge and subject matter expertise
74:24 

74:24 within our small group. So, we need to
74:25 

74:25 branch out and get input from a variety
74:28 

74:28 of different stakeholders. So, what is
74:30 

74:30 the engagement? Well, we envision this
74:32 

74:32 to be streamlined coordination and
74:35 

74:35 engagement with the industry via the
74:37 

74:37 DDSG and others. So, we recognize that
74:41 

74:41 the DDSG provides us access to a large
74:44 

74:44 group of different industry
74:45 

74:45 stakeholders. So, we want to leverage
74:46 

74:46 that for our mutual benefit. Um, in
74:50 

74:50 terms of supporting the pulled funds,
74:52 

74:52 how could this take place? Well, we see
74:55 

74:55 this as really three different steps.
74:57 

74:57 Three steps are involved with this
74:59 

74:59 engagement. uh so first would be
75:01 

75:01 establishment of the representation from
75:04 

75:04 the uh from industry and secondly
75:07 

75:07 getting input on products and then third
75:11 

75:11 awareness and adoption.
75:13 

75:13 So I'll elaborate on what I mean by
75:15 

75:15 these. So again those three steps at the
75:19 

75:19 top establishing representation. So we
75:22 

75:22 know the DDSG is up and running that has
75:24 

75:24 great participation in meetings like
75:26 

75:26 today's and uh our poolled fund the two
75:30 

75:30 pulled funds are looking to coordinate
75:32 

75:32 closely with the DDSG leadership to
75:35 

75:35 identify a subset of the DDSG core
75:38 

75:38 members to join our industry advisory
75:40 

75:40 group and this would be the entity um at
75:43 

75:43 the executive level that would provide
75:45 

75:45 um some highle um strategic input to the
75:49 

75:49 poolled fund work Um but there's more to
75:52 

75:52 it and we've talked a little bit about
75:54 

75:54 getting that technical feedback. So
75:56 

75:56 that's another critical piece here. So
75:58 

75:58 once we establish this industry advisory
76:00 

76:00 group um and and we've made some strides
76:03 

76:03 here already even before um you know the
76:06 

76:06 DDSG efforts got in full swing here but
76:10 

76:10 uh we're looking for that industry
76:11 

76:11 advisory group to identify members of
76:14 

76:14 technical working groups as needed. So
76:17 

76:17 as we continue the poolled fund work on
76:19 

76:19 both sides, bridge and infrastructure,
76:21 

76:21 there's going to be specific tasks where
76:23 

76:23 we want that industry input on
76:26 

76:26 particular activities that we're doing
76:27 

76:27 and we need that subject matter
76:29 

76:29 expertise. So we would seek for the
76:32 

76:32 industry advisory group to be that
76:34 

76:34 mechanism to identify participants in
76:37 

76:37 the technical working groups. Um
76:41 

76:41 this would not be just a a a random
76:44 

76:44 request. Please send us some names, but
76:46 

76:46 rather we'll work closely with the I A
76:50 

76:50 to define the expectations.
76:52 

76:52 Oops,
76:54 

76:54 sorry about that. Uh, we would define
76:56 

76:56 the needs and expectations for the
76:59 

76:59 participants like preferred
77:00 

77:00 qualifications. What type of people are
77:02 

77:02 we looking for?
77:04 

77:04 And again, this would be like an as
77:06 

77:06 needed basis. Each technical working
77:07 

77:07 group could be a little bit different
77:08 

77:08 depending on what the task is, the size
77:11 

77:11 could be different, the duration, etc.
77:13 

77:13 And that would all be defined by the
77:14 

77:14 poolled funds so that we can get the
77:16 

77:16 right participants.
77:20 

77:20 So after having a technical working
77:22 

77:22 group in place and having that mechanism
77:24 

77:24 to get input from the industry
77:26 

77:26 stakeholders, it's really up to the
77:27 

77:27 poolled fund teams to develop and and
77:29 

77:29 and work on those technical work
77:31 

77:31 products. We're getting that good input
77:33 

77:33 from a variety of stakeholders. Um and
77:36 

77:36 then the poolled fund teams are doing,
77:39 

77:39 you know, the bulk of the work here. And
77:41 

77:41 we would be sharing the draft products
77:43 

77:43 with the DDSG and others um because we
77:47 

77:47 want people to test it, to try it, to
77:49 

77:49 review it and provide us additional
77:52 

77:52 feedback.
77:54 

77:54 Oops, I keep going the wrong way. Um so
77:57 

77:57 lastly, after we get that additional
77:59 

77:59 feedback, the poolled funds are looking
78:01 

78:01 to finalize the work products and and
78:04 

78:04 publish them, adopt them in some formal
78:06 

78:06 way. So that this part in yellow, the
78:08 

78:08 ASHTO endorsed open standards is the
78:11 

78:11 ultimate goal. Uh I mentioned earlier
78:14 

78:14 that the process for doing this is not
78:16 

78:16 established yet, but um groups are
78:18 

78:18 actively working on figuring this out. I
78:20 

78:20 know J Stan needs a lot of support in
78:22 

78:22 from all the states to really um and I
78:26 

78:26 think I saw Trisha Stfansky on the on
78:29 

78:29 the meeting here. I'm sure she would
78:30 

78:30 have a lot to say if if I asked her, but
78:33 

78:33 uh we're looking for states to have to
78:35 

78:35 support JStand in those efforts so that
78:37 

78:37 we can have this governance process for
78:39 

78:39 digital work products. ASHTO had a has a
78:43 

78:43 a process if we want to publish a manual
78:46 

78:46 and that's what we did on the bridge
78:48 

78:48 side for with the IDM that I mentioned
78:50 

78:50 earlier. It was relatively smooth to
78:52 

78:52 work through the ASHTDO committee on
78:54 

78:54 bridges and structures to get them to
78:56 

78:56 adopt a PDF and then formally publish
78:60 

78:60 it. So it's made available. Things are
79:02 

79:02 very different when it comes to digital
79:04 

79:04 standards and electronic files
79:07 

79:07 essentially these these an IDS file is
79:10 

79:10 not not a PDF that you can just read. So
79:13 

79:13 there's a lot behind that yellow, but
79:15 

79:15 that's that's the ultimate goal and the
79:17 

79:17 input along the way from these various
79:19 

79:19 stakeholders will will help us achieve
79:21 

79:21 that ultimate goal.
79:25 

79:25 All right, just a couple more slides
79:27 

79:27 here. I want to give a little more um
79:29 

79:29 explanation of what we envision these
79:31 

79:31 the IG the industry advisory group um
79:35 

79:35 and what the technical working groups
79:37 

79:37 would look like. So on the IG side, we
79:40 

79:40 would envision this to be a little bit
79:42 

79:42 of a longer term commitment having
79:44 

79:44 consistent personnel, fewer meetings, uh
79:47 

79:47 more at the uh executive level, more
79:50 

79:50 strategic and vision oriented. And we
79:52 

79:52 would look to have one champion from
79:54 

79:54 each identified industry group that we
79:56 

79:56 want to collaborate with. And then on
79:59 

79:59 the technical working group side, this
80:00 

80:00 is potentially a shorter term commitment
80:03 

80:03 depending on the particular task. Uh, so
80:06 

80:06 the people involved would would vary
80:08 

80:08 based on what the task is. This could
80:12 

80:12 potentially be more frequent meetings, a
80:13 

80:13 longer duration, you know, with
80:15 

80:15 homework, so to speak, um, people
80:17 

80:17 reviewing items, and it would be much
80:20 

80:20 more technical and detail oriented. It
80:23 

80:23 doesn't necessarily mean that
80:24 

80:24 participants in the technical working
80:26 

80:26 groups need to be IFC experts or digital
80:29 

80:29 delivery experts, but they may need to
80:31 

80:31 be experts in their particular area of
80:34 

80:34 expertise. um that subject matter,
80:35 

80:35 whether that has to do with um lighting
80:39 

80:39 fixtures or um pre-cast
80:43 

80:43 um bridge I mean beam fabrication or
80:45 

80:45 whatever the case may be.
80:48 

80:48 Uh and there could be in this case
80:49 

80:49 multiple representatives from industry
80:52 

80:52 groups and also state DOS.
80:55 

80:55 Uh
80:57 

80:57 let's see on the on the timeline side. I
80:60 

80:60 don't have uh anything on the slide for
81:02 

81:02 this but I know um John mentioned that
81:05 

81:05 their needs are are pretty imminent to
81:07 

81:07 get some input from stakeholders in the
81:09 

81:09 coming months. I know we've already made
81:11 

81:11 some um efforts to we have our first
81:14 

81:14 technical working group established on
81:16 

81:16 the bridge side uh coordinating with the
81:18 

81:18 steel bridge and concrete bridge
81:20 

81:20 industry. Uh so we have kind of gone
81:22 

81:22 through this process once before working
81:25 

81:25 with umbrella organizations for steel
81:27 

81:27 and concrete to identify those members
81:29 

81:29 but that will not be sufficient. We need
81:32 

81:32 we need we will need more technical
81:33 

81:33 working groups going into the future.
81:35 

81:35 BIM for bridges will need more groups as
81:37 

81:37 well you know over the next 6 to 12
81:39 

81:39 months.
81:42 

81:42 So, in closing, uh you might be
81:44 

81:44 wondering as a member of the DDSG
81:48 

81:48 community, what can you do to support
81:50 

81:50 the poolled funds? Well, if you're from
81:52 

81:52 a state DOT, you can certainly sponsor a
81:55 

81:55 poolled fund and get involved. If you're
81:57 

81:57 in bridge but not infrastructure or vice
81:59 

81:59 versa, you can join the other one. If
82:00 

82:00 you're in neither, you could join. Jim
82:03 

82:03 Hower mentioned um another software
82:06 

82:06 certification and validation pulled fund
82:08 

82:08 that's getting started up. So that's
82:09 

82:09 another opportunity.
82:11 

82:11 Also, you can consider doing pilot
82:13 

82:13 projects using the poolled fund open
82:15 

82:15 data standards.
82:17 

82:17 Those are ready to go on the bridge side
82:19 

82:19 for the design to construction exchange
82:21 

82:21 and other standards from infrastructure
82:23 

82:23 and more on the bridge side will be
82:24 

82:24 forthcoming. Um state DOS can also
82:27 

82:27 support Jstan and other groups to
82:29 

82:29 establish that governance of data
82:31 

82:31 standards. We want to have an ASHTDO
82:34 

82:34 endorsement process to make all this
82:35 

82:35 successful. Um so state DOT support is
82:38 

82:38 important for that. If you are on the
82:41 

82:41 software vendor side uh I wanted to note
82:45 

82:45 that um there is an active software
82:47 

82:47 advisory group for BIM for Bridges right
82:49 

82:49 now. It is open to all vendors. So if
82:52 

82:52 you're from a technology provider or
82:53 

82:53 software vendor and you want to um get
82:56 

82:56 involved, you can reach out to me. Um
82:59 

82:59 now that u bin for infrastructure is is
83:02 

83:02 um at a similar um point in their
83:05 

83:05 efforts uh with developing data
83:08 

83:08 standards we there are also plans and
83:11 

83:11 and things underway to integrate our
83:13 

83:13 outreach to software vendors. So BIM for
83:15 

83:15 bridges and BIM for infrastructure will
83:17 

83:17 will be integrating our our efforts
83:21 

83:21 here.
83:22 

83:22 If you're not part of the two groups um
83:25 

83:25 the first two groups I mentioned if
83:26 

83:26 you're considered if you consider
83:28 

83:28 yourself another stakeholder uh you can
83:30 

83:30 certainly watch for periodic updates
83:33 

83:33 about what the poolled funds are doing
83:35 

83:35 through the DDSG through the future
83:37 

83:37 meetings here and other venues. We are
83:40 

83:40 frequently presenting on uh status
83:43 

83:43 updates of the two poolled funds such as
83:45 

83:45 at IHEA at the um building smart USA
83:48 

83:48 events etc. And if you want to get more
83:51 

83:51 involved, you can certainly work with
83:53 

83:53 your respective industry groups I AG
83:56 

83:56 representatives once those are
83:57 

83:57 identified to see where you can
83:60 

83:60 contribute.
84:02 

84:02 That is uh the general um vision. And
84:07 

84:07 with that, Roger and Matt, we can move
84:10 

84:10 on to our open discussion time and and
84:12 

84:12 take questions and hear other ideas from
84:15 

84:15 folks.
84:17 

84:17 >> Yeah. Um thanks Billy. Um, so do you
84:21 

84:21 want to put put up I I thought you had a
84:24 

84:24 like more specific what did you need the
84:27 

84:27 DDSG to do, but I guess you're saying
84:29 

84:29 what do you need industry advisory for
84:32 

84:32 and what do you need technical advisory
84:35 

84:35 for? Um,
84:40 

84:40 >> uh, is is this slide helpful? I
84:43 

84:43 >> Yeah, I guess so. The immediate need
84:46 

84:46 would be our the two poolled funds um to
84:49 

84:49 coordinate closely with the DDSG
84:51 

84:51 leadership on identifying those folks to
84:54 

84:54 >> Right. I I think we've got the coordin
84:57 

84:57 sorry
84:60 

84:60 >> I think we understand coordination. I
85:02 

85:02 guess I was looking more for what is it
85:04 

85:04 you want to get out of the AG? I guess
85:07 

85:07 that's on the next slide. So we could
85:10 

85:10 figure out how to help in the
85:12 

85:12 accomplishment of that. Well, I think
85:15 

85:15 we'll be looking for buyin on the things
85:18 

85:18 that we're doing and have a
85:19 

85:19 understanding among that group so that
85:22 

85:22 when it comes time among other reasons,
85:24 

85:24 but also when it comes time to get that
85:26 

85:26 more technical input, they they have the
85:29 

85:29 um
85:30 

85:30 you know the knowledge and the
85:33 

85:33 um I guess they so they feel empowered
85:36 

85:36 to find those folks to participate
85:39 

85:39 working groups
85:41 

85:41 >> and other ideas you know
85:43 

85:43 >> want to chime And go ahead, Roger.
85:47 

85:47 >> Talking to what maybe where you're
85:48 

85:48 getting at is what what specifically do
85:50 

85:50 we need to engage on?
85:52 

85:52 >> Yeah. I mean, if you want people
85:54 

85:54 involved, what are you going to ask?
85:55 

85:55 What are you going to be looking for
85:57 

85:57 from them, I guess, so that, you know,
85:60 

86:00 they would know and we would know how
86:02 

86:02 that fits with what the DDSG is trying
86:04 

86:04 to do with industry stakeholders. I
86:08 

86:08 guess that's where we're trying to come
86:09 

86:09 together here, right? So
86:12 

86:12 >> well I think the the general products
86:14 

86:14 right are are collaboration on the data
86:16 

86:16 dictionary the information requirements
86:18 

86:18 for the exchange the information
86:20 

86:20 delivery manual and testing the
86:22 

86:22 information delivery specification u
86:25 

86:25 making sure that you know if you're a
86:26 

86:26 vendor it works in your product if
86:27 

86:27 you're an equipment manufacturer your
86:30 

86:30 equipment can receive it and it's
86:31 

86:31 structured in a manner that you can
86:33 

86:33 consume it um or what what changes need
86:38 

86:38 to be happen need to happen on one side
86:40 

86:40 or the other in in order for that to
86:41 

86:41 happen, right? Going back to the
86:43 

86:43 piloting and testing, right? Um getting
86:45 

86:45 engaged in the in the pilot engagements,
86:47 

86:47 right? So, it's more of a table setting
86:49 

86:49 for some of those activities, but as we
86:52 

86:52 before we get out and start testing some
86:54 

86:54 of this, I think there's at the
86:56 

86:56 technical level, we want to make sure we
86:58 

86:58 get that early feedback. So, you know,
87:00 

87:00 once you once you start piloting on say
87:02 

87:02 a project, time is of the essence,
87:05 

87:05 right? Um so, at least have have
87:08 

87:08 everybody in the right place. um and
87:10 

87:10 know that there are resources to enable
87:12 

87:12 to do that. I don't know does that help
87:16 

87:16 for sometimes I talk too much and and it
87:19 

87:19 makes it more confusing.
87:26 

87:26 >> Yeah, I heard some things there.
87:28 

87:28 collaboration on on the different work
87:30 

87:30 products like exchanges, data
87:32 

87:32 dictionaries,
87:34 

87:34 um getting engagement in pilots and uh
87:38 

87:38 getting early feedback on on uh I guess
87:42 

87:42 technical development
87:48 

87:48 and I think that's probably in this
87:50 

87:50 slide. um finalizing work products,
87:53 

87:53 sharing drafts,
87:55 

87:55 um developing products.
88:00 

88:00 We think the idea is to go through the
88:02 

88:02 DDSG leadership on the groups that are
88:05 

88:05 already represented
88:07 

88:07 >> to help identify
88:09 

88:09 >> who who we should go to as we engage
88:12 

88:12 more in a in an industry advisor group
88:15 

88:15 because I know as as you pointed out
88:17 

88:17 before that's not the focus of the DDSG
88:20 

88:20 but we may be talking to the same people
88:22 

88:22 in some of these uh industry groups um
88:26 

88:26 at at the industry advisory group level
88:29 

88:29 right and and their role is to help
88:31 

88:31 identify people that can engage in these
88:35 

88:35 technical working groups so to speak
88:37 

88:37 that'll be like the industry advisor
88:39 

88:39 group would be more commitment
88:42 

88:42 >> right but less frequently engaging
88:45 

88:45 um technical working groups would have a
88:47 

88:47 a short-term more frequent engagement
88:50 

88:50 right like you like you pointed out
88:52 

88:52 Julie on a particular thing.
88:57 

88:57 >> Yeah. Yeah. And I guess trying to figure
88:59 

88:59 out um well it looks like the technical
89:03 

89:03 groups, you know, are pretty much in the
89:05 

89:05 domain of the of the um uh pool funds,
89:10 

89:10 but then at the advisory group level,
89:12 

89:12 how do we make sure we're not asking
89:15 

89:15 people the same for the same things and
89:18 

89:18 and coordinate on that piece? So meeting
89:22 

89:22 with or yeah, us meeting to figure that
89:25 

89:25 out. That's what we're starting to do
89:27 

89:27 here.
89:29 

89:29 >> Yeah. And just to elaborate a little
89:31 

89:31 bit, Roger, kind of two things. So, on
89:33 

89:33 the front end, um I mentioned that we
89:36 

89:36 have a technical working group for for
89:39 

89:39 um concrete and steel bridge industry
89:41 

89:41 folks. Um
89:43 

89:43 >> that's to to help us with input on the
89:46 

89:46 fabrication detail exchange. So it would
89:48 

89:48 be difficult for me to just reach out to
89:51 

89:51 random steel fabricators or concrete you
89:54 

89:54 know pre-casters to try to ask them to
89:57 

89:57 participate. So instead I went to the
89:59 

89:59 National Steel Bridge Alliance and
90:01 

90:01 National Concrete Bridge Council. Those
90:03 

90:03 are umbrella organizations and I
90:04 

90:04 explained what the needs are. So those
90:06 

90:06 two champions um would be members of
90:09 

90:09 this IAG and they're at the executive
90:10 

90:10 level of those umbrella organizations
90:13 

90:13 and we worked with them explained what
90:15 

90:15 our needs were and then they identified
90:17 

90:17 some participants for our technical
90:18 

90:18 working group and so that smaller group
90:21 

90:21 would provide input but then in the
90:24 

90:24 lower right corner where we're saying we
90:26 

90:26 would share draft products this would be
90:27 

90:27 with the full DDSG. So when we have
90:29 

90:29 these draft products the the IDM the IDS
90:32 

90:32 the data dictionary we want that to be
90:36 

90:36 um used by broader industry to to get
90:39 

90:39 you know for people to test it out try
90:41 

90:41 it on projects or try it on internal
90:43 

90:43 initiatives and and provide additional
90:46 

90:46 feedback so that's where the DDSG comes
90:48 

90:48 in as well is we have a we have a
90:50 

90:50 mechanism to share and get the
90:52 

90:52 information to certain people and to and
90:54 

90:54 to walk them through it and so I would
90:56 

90:56 envision that to be part of this as
91:04 

91:04 Hey Julie, can I add a little bit more
91:05 

91:05 to that?
91:07 

91:07 >> Sure.
91:07 

91:07 >> You know, to me, part of this is
91:09 

91:09 communicating with one voice what is
91:11 

91:11 needed. I mean, we have BIM week and you
91:14 

91:14 know, that developed through the first
91:15 

91:15 poolled fund. It started with National
91:16 

91:16 Cops Technology. We'd have our COBS
91:20 

91:20 meeting and then we'd have the poolled
91:21 

91:21 fund meeting and then we got BIM for
91:23 

91:23 infrastructure and it grew into a full
91:25 

91:25 BIM full BIM week. Okay, that's one
91:27 

91:27 meeting. But you're talking about
91:29 

91:29 meeting and communicating with high high
91:31 

91:31 level executives. You can't invite them
91:34 

91:34 to BIM week. You can't invite them to
91:35 

91:35 Ashto Cobbs. You can't buy them
91:37 

91:37 committee on construction GTCS and every
91:40 

91:40 single two months having a meeting that
91:42 

91:42 you want to participate. So, you know,
91:44 

91:44 we can't ask them to come to our stuff
91:46 

91:46 and everyone else. So, to me, it's a
91:48 

91:48 central way to coordinate with all those
91:50 

91:50 upper level executives without having
91:52 

91:52 meeting overload for them. I mean, we
91:54 

91:54 can't ask for two weeks of their time
91:56 

91:56 every year for various meetings. So,
91:58 

91:58 that's where I see part of it is trying
92:01 

92:01 to prevent that and really communicate
92:02 

92:02 with that ind industry advisory group.
92:04 

92:04 Now, both funds, pool funds are going to
92:06 

92:06 have specific people they need at that
92:08 

92:08 industry, you know, advisory group. We
92:10 

92:10 have NS NSBA and AC or American Concrete
92:15 

92:15 ACIC.
92:17 

92:17 >> NCBC ACI just became a member. Yeah,
92:20 

92:20 NCBC is a new one to me. um you know
92:22 

92:22 they got CRSI participating in that and
92:26 

92:26 so we're going to have our unique
92:27 

92:27 members to both poolled funds but we're
92:29 

92:29 still going to have AGC is going to be
92:31 

92:31 common to both of them um ARPA
92:34 

92:34 ACEC they're you know those are members
92:37 

92:37 that we need to communicate with one
92:39 

92:39 voice while at the same time having them
92:41 

92:41 champion these digital delivery efforts
92:43 

92:43 without overloading them with meetings.
92:46 

92:46 So, you know, some of them aren't going
92:47 

92:47 to be super interested in technical
92:49 

92:49 stuff. I mean, they're we start getting
92:51 

92:51 too down into the weeds with them, their
92:52 

92:52 eyes won't light up like uh Rick Bryce
92:54 

92:54 is and Lyn Heels with Calr. I mean, they
92:57 

92:57 love that data, but not everyone has
92:59 

92:59 time to get into that. So, sorry, I I I
93:03 

93:03 have a similar habit as John where if I
93:05 

93:05 talk too long, it becomes a little bit
93:07 

93:07 of overload, but that's where I see it
93:10 

93:10 aligning.
93:14 

93:14 >> All good, Jim. And then if you want
93:15 

93:15 separate meetings where you want to get
93:17 

93:17 into the weeds, I would separate
93:18 

93:18 schedule a separate meeting for the the
93:20 

93:20 people interested in that really
93:22 

93:22 technical information.
93:27 

93:27 >> Yeah. So these kinds of updates around
93:30 

93:30 what's going on with the poolled funds
93:32 

93:32 are good to then have here so everyone
93:35 

93:35 hears it in if this is a place to hear
93:38 

93:38 things in one place that's one role we
93:41 

93:41 can we think the DDSG can fill.
93:48 

93:48 Julie is the the the industry advisory
93:52 

93:52 group. They're kind of supplementary to
93:56 

93:56 already
93:57 

93:57 the participating
93:60 

93:60 state members of each pulled fund.
94:04 

94:04 Correct.
94:06 

94:06 >> That is correct. And they represent
94:08 

94:08 groups that are not direct sponsors of
94:11 

94:11 the pulled fund. So essentially some of
94:15 

94:15 the groups that um
94:17 

94:17 uh Jim just mentioned the AGC, ARTBA
94:22 

94:22 um on the bridge side, we would you
94:24 

94:24 would want to include the NCBC and SBA
94:28 

94:28 um ACEC
94:30 

94:30 um I'm sure I'm leaving out others, but
94:32 

94:32 um
94:34 

94:34 that would be the intent is to capture
94:36 

94:36 stakeholders that are not otherwise
94:38 

94:38 directly involved or sponsoring the
94:39 

94:39 poolled fund.
94:41 

94:41 And could that also include nonpold fund
94:46 

94:46 member states as well?
94:50 

94:50 >> Oh, that's a good question. I don't know
94:51 

94:51 if we've directly considered that.
94:55 

94:55 >> Are you talking about participating at
94:58 

94:58 the industry advisory group level?
95:00 

95:00 >> Yes.
95:03 

95:03 >> I guess
95:05 

95:05 I wouldn't be opposed to it. I just not
95:07 

95:07 sure how it would line up. I mean, if
95:09 

95:09 they're not participating in the poolled
95:11 

95:11 fund, I mean, are you looking at them to
95:13 

95:13 champion it? I mean, I would be more
95:14 

95:14 than happy. I mean, if they want to do
95:16 

95:16 the supplemental and say, "Hey, we want
95:17 

95:17 to do a IFC model for information only
95:20 

95:20 or do a mold with IFC and they need a
95:22 

95:22 little help getting started." Yeah, they
95:24 

95:24 can participate in that sub um in that
95:27 

95:27 part of it. But champion what the
95:30 

95:30 poolled funds are delivering, it seems
95:32 

95:32 like they'd have to kind of participate
95:34 

95:34 in the poolled fund for that. That being
95:36 

95:36 said, you know, if it's an industry
95:38 

95:38 group, they don't directly I know NSBA
95:41 

95:41 consider joining I think for 10,000 a
95:44 

95:44 year to the BIM for Bridgepoolled Fund,
95:46 

95:46 which is great because um nonprofit
95:48 

95:48 organizations can join poolled funds.
95:51 

95:51 But I if you come up with an example on
95:54 

95:54 a non-pulled fund participation state
95:56 

95:56 wanting to join the industry advisory
95:58 

95:58 group, yeah, I'm more than happy to
95:59 

95:59 discuss it and if it makes sense, I
96:02 

96:02 would be willing to accept that, but I
96:03 

96:03 would have to talk internally with our
96:05 

96:05 research and analytics department to
96:06 

96:06 make sure they're agreeable to it.
96:10 

96:10 Uh I I don't claim to know or understand
96:14 

96:14 what processes each state agency has to
96:18 

96:18 determine whether they participate in a
96:22 

96:22 pulled fund or not. So I I don't I guess
96:25 

96:25 the question in my mind was just as
96:27 

96:27 there may have been some states out
96:30 

96:30 there that maybe had an interest in the
96:32 

96:32 pulled fund and for whatever reason they
96:34 

96:34 ended up not being a funding
96:36 

96:36 participating agency but they may have
96:40 

96:40 you know expertise or staff that are
96:43 

96:43 doing work in that area. And so that
96:46 

96:46 this may be an opportunity to kind of
96:47 

96:47 bring them into the conversation and get
96:50 

96:50 that dialogue
96:52 

96:52 acknowledging that you would you would
96:55 

96:55 optimistically
96:57 

96:57 hope that if you've got an interest in
96:59 

96:59 what the pulled funds were doing is then
97:02 

97:02 you would become a contributing member
97:03 

97:03 and get involved.
97:06 

97:06 >> So from that perspective, if they really
97:08 

97:08 want to contribute and add it, we can
97:10 

97:10 always use more help doing the technical
97:12 

97:12 working group reviews. I mean it's a lot
97:15 

97:15 of this is volunteer time by DOT
97:17 

97:17 employees and some of it can be consu
97:19 

97:19 time consuming especially reviewing you
97:21 

97:21 know detailed data dictionaries and
97:24 

97:24 things like that. So if there's people
97:25 

97:25 that want to participate who aren't
97:27 

97:27 poolled fund members but are willing to
97:29 

97:29 put time in or doing their own state
97:31 

97:31 initiatives and want to work on
97:32 

97:32 reviewing some of the technical
97:34 

97:34 deliverables I'm more than happy to have
97:36 

97:36 you. That would be awesome. I think if
97:38 

97:38 you ask Julie or John how much work it
97:40 

97:40 is to, you know, it's people got to fit
97:42 

97:42 this time in, you know, within their
97:45 

97:45 work schedules and, you know, every
97:47 

97:47 everyone's do more with less. So, their
97:49 

97:49 Saturday, Sundays spent doing this. So,
97:51 

97:51 if we can have more people doing that,
97:53 

97:53 even if they're not contributing,
97:56 

97:56 you know, from a funding level, I would
97:57 

97:57 be happy to have that. Um, now, if
98:00 

98:00 they're doing that, they, you know, they
98:02 

98:02 could probably still participate in BIM
98:04 

98:04 week and things like that, but it would
98:05 

98:05 be on their own expense. So we we do
98:07 

98:07 have if you participate you know our
98:09 

98:09 poolled fund member we do pay for travel
98:11 

98:11 for one member if you want to bring
98:12 

98:12 additional members to BIM week there is
98:14 

98:14 a supplemental you can do for extra
98:16 

98:16 funding for that that applies to BIM for
98:18 

98:18 bridge and BIM for infra um but yeah if
98:21 

98:21 there's people that want to participate
98:22 

98:22 on the technical working group and help
98:24 

98:24 review IDMs data dictionaries um IDS's
98:28 

98:28 and all that stuff uh more than happy to
98:30 

98:30 have you even if you're not contributing
98:34 

98:34 usually I don't get too many people
98:36 

98:36 volunteering trying to do free work, but
98:39 

98:39 but if there's someone, you know, and
98:41 

98:41 that's a lot of what it is. You know, I
98:42 

98:42 I this is additional duties beyond my
98:45 

98:45 regular regular job. So,
98:48 

98:48 >> so it it seems like that could I mean,
98:51 

98:51 one thing that DDSG can do is help
98:53 

98:53 identify, okay, what technical working
98:56 

98:56 groups are out there and share. So, one
98:59 

98:59 of our goals is to, you know, share
99:01 

99:01 information so there's common
99:03 

99:03 understanding and then people could
99:05 

99:05 advance that to getting involved if they
99:07 

99:07 were interested whether they're a member
99:09 

99:09 or not by reaching out to the technical
99:12 

99:12 working groups at the industry level. I
99:16 

99:16 think that's where we still maybe have a
99:17 

99:17 few things to figure out like Matt's got
99:21 

99:21 a question in the chat about do you want
99:24 

99:24 ACEC on the industry advisor group or
99:27 

99:27 they're on the DDSG you know how do we
99:30 

99:30 resolve those kinds of things
99:33 

99:33 collectively in a way that like we said
99:36 

99:36 at the beginning doesn't create
99:38 

99:38 duplication of effort and uh time etc.
99:41 

99:41 So, I don't know, Matt, if you want to
99:43 

99:43 say anything about your question, but
99:51 

99:51 you could
99:52 

99:52 >> we we could bring him in and unmute him.
99:54 

99:54 I think Brackley might be able to do
99:57 

99:57 that if if he chooses to. But I think
99:60 

99:60 that I mean his the way I'm interpreting
100:02 

100:02 his question, which I kind of agree a
100:05 

100:05 little bit with, is that you know we we
100:07 

100:07 have so we've got an ACE represent
100:11 

100:11 representative that was selected by ACE
100:15 

100:15 as as representing them and their
100:18 

100:18 members. So you know whether the person
100:22 

100:22 on the DDSG
100:24 

100:24 is the appropriate person from ACEC to
100:27 

100:27 be on the I A and industry advisory
100:32 

100:32 group I think would be determined by
100:36 

100:36 ACEC themselves.
100:39 

100:39 Um because sometimes they've elected to
100:41 

100:41 have somebody who is one of their
100:45 

100:45 members uh a company or membership
100:49 

100:49 within their organization
100:52 

100:52 uh as the representative on the DDSG and
100:55 

100:55 not necessarily someone who is an
100:57 

100:57 employee of their association.
101:00 

101:00 So there's that question of if you know
101:03 

101:03 we want ACEC to have somebody on the I A
101:08 

101:08 then giving them the opportunity to say
101:10 

101:10 yes or no and you know elect who they
101:13 

101:13 want and then that would be the
101:15 

101:15 mechanism for them to go to their
101:18 

101:18 members about who's got the specific
101:20 

101:20 expertise
101:22 

101:22 to work on each of these smaller
101:24 

101:24 technical working groups as the items
101:26 

101:26 come up and they would be that cond
101:29 

101:29 conduit to get additional representation
101:32 

101:32 of their member community involved at
101:35 

101:35 the technical working group level
101:36 

101:36 because of what you know their their
101:39 

101:39 members provide.
101:42 

101:42 And Matt, I'll just add that you know
101:43 

101:43 we've done outreach over the last couple
101:45 

101:45 of years with um some of these key
101:48 

101:48 groups and I know Will Sharp is on the
101:50 

101:50 line. He can chime in with more
101:52 

101:52 background on that. So this this is not
101:54 

101:54 a brand new thing. It's kind of been
101:56 

101:56 already started, but we're This is how
101:59 

101:59 DDSG can like, you know, supplement what
102:02 

102:02 we've already done. But Will, do you
102:03 

102:03 want to elaborate on that a little bit?
102:07 

102:07 >> Yeah, sure, Julie. Yeah, we we've been
102:09 

102:09 at this for several years, and I guess a
102:12 

102:12 couple of key takeaways. We definitely
102:14 

102:14 want to leverage the DDSG. We do think a
102:17 

102:17 subset of the core members would be very
102:19 

102:19 beneficial to have on the industry
102:22 

102:22 advisory group. Uh, but as Julie noted,
102:25 

102:25 there's also a number of other groups
102:27 

102:27 that we're going to need to engage as
102:28 

102:28 well, like NSBA and NCBC and other
102:32 

102:32 specialists. So, we we see that as a way
102:34 

102:34 for the the two groups to work together.
102:37 

102:37 Um, Julie, as you noted, too, there's a
102:40 

102:40 lot of opportunities to get plugged in
102:42 

102:42 here. You know, one of the things with
102:44 

102:44 the BIM for bridging structures pulled
102:45 

102:45 fund and lessons learned from phase one
102:48 

102:48 is we want to develop the draft
102:50 

102:50 deliverables and get broad industry
102:52 

102:52 input and we definitely want to leverage
102:54 

102:54 the DDSG to get the word out on that get
102:58 

102:58 get their input you know get comments on
103:00 

103:00 our draft uh national standards that are
103:03 

103:03 developed because different stakeholders
103:05 

103:05 use these in different ways. So that is
103:07 

103:07 one way like I said we really want to
103:09 

103:09 leverage this group. We think this is a
103:11 

103:11 great group to leverage to get that
103:12 

103:12 broader input, you know, before we
103:15 

103:15 finalize and put out these ASHTO
103:17 

103:17 endorsed open standards.
103:20 

103:20 And I guess one last thing, Julie, we,
103:22 

103:22 you know, at BM week last year, we had a
103:25 

103:25 lot of I think real productive
103:26 

103:26 discussions between BIM for
103:28 

103:28 infrastructure and BIM for rich
103:30 

103:30 structures and this will be a common
103:32 

103:32 group to both the pool funds. you know,
103:34 

103:34 thought we thought that was very
103:36 

103:36 important to there's so much overlap
103:38 

103:38 between the pool funds that having uh
103:40 

103:40 you know, an industry advisory group to
103:42 

103:42 serve both pulled funds we thought was
103:44 

103:44 was very important as well. So, so
103:47 

103:47 hopefully that clarifies a few things.
103:51 

103:51 >> Yeah, thanks. Well,
103:52 

103:52 >> yeah, I think that's helpful, Will. I
103:54 

103:54 think there's still maybe a little
103:55 

103:55 question about overlap potential for
103:58 

103:58 overlap and how we would um try to make
104:02 

104:02 you know minimize it to the greatest
104:03 

104:03 extent possible manage it between the
104:06 

104:06 DDSG and the EUR and the poolled funds
104:10 

104:10 industry advisory group because it does
104:13 

104:13 seem like there's a common somewhat
104:16 

104:16 common ask for participants in those
104:20 

104:20 different groups. So, I think that may
104:22 

104:22 be still something to continue trying to
104:25 

104:25 figure out,
104:27 

104:27 >> right? Well, we we did talk about this
104:29 

104:29 in in detail in November, uh, Roger, and
104:32 

104:32 like I said, I think the pool funds
104:34 

104:34 vision on this is pretty clear, and, you
104:37 

104:37 know, we definitely see the need to get
104:39 

104:39 this stood up and going and and like I
104:41 

104:41 mentioned, I I do think the the DDSG,
104:44 

104:44 many of the core members of that group
104:47 

104:47 will be on our IG group as well. So, you
104:49 

104:49 know, there's definitely going to be
104:51 

104:51 good overlap, good coordination there uh
104:53 

104:53 to get that industry input, but like I
104:56 

104:56 mentioned, we're going to have
104:57 

104:57 additional members there as well. So, so
104:60 

105:00 I really think that's the best approach
105:02 

105:02 moving forward to get us what we need
105:04 

105:04 for the food funds and to have that
105:06 

105:06 tight coordination with the uh the DDSG
105:08 

105:08 as well.
105:15 

105:15 >> And I don't know, Jim Hober, I don't
105:16 

105:16 know if you have anything to add on
105:17 

105:17 that. I know said we talked about this a
105:19 

105:19 lot on Friday at Memo Week between the
105:21 

105:21 two pool funds.
105:23 

105:23 >> Yeah.
105:23 

105:23 >> But any anything to add, Jim?
105:25 

105:25 >> Yep. Ju I'll add a little bit more. You
105:26 

105:26 know, ARPA, AGC, and ACEC nationally all
105:30 

105:30 have um a position paper on digital
105:33 

105:33 delivery. And that's the level that
105:36 

105:36 we're looking at for this digital
105:37 

105:37 delivery stakeholder group leadership,
105:40 

105:40 you know, industry advisory group. they,
105:42 

105:42 you know, they're not going to want to
105:43 

105:43 sit there for three hours and get into
105:45 

105:45 the technical details, but they need to
105:47 

105:47 communicate to their organizations what
105:49 

105:49 we're doing, how it benefits them, make
105:51 

105:51 sure we're aligning with what they need
105:53 

105:53 in order to do their jobs. And, you
105:56 

105:56 know, and we can't be having, you know,
105:58 

105:58 the whole goal was to prevent meeting
105:60 

105:60 overload for these people. You know, we
106:01 

106:01 can't have BIM for Bridge asking them
106:03 

106:03 questions one day, BIM for
106:05 

106:05 infrastructure asking their digital
106:06 

106:06 delivery lead. you know, we need to
106:08 

106:08 align with one voice. So, we're asking
106:09 

106:09 the same questions in a unified voice
106:12 

106:12 and getting responses. So, we need to
106:14 

106:14 make sure we align with their their
106:15 

106:15 policy positions on digital delivery. We
106:18 

106:18 give them the information they want. We
106:20 

106:20 get the information we need and they're
106:21 

106:21 championing at a very high level and
106:24 

106:24 they need to know about these digital
106:25 

106:25 delivery initiatives. Not, you know,
106:27 

106:27 they definitely don't need to be in the
106:29 

106:29 technical working group. I'm sure Matt
106:31 

106:31 wants nothing to do with that technical
106:32 

106:32 working group. Not that he wouldn't be
106:34 

106:34 interested, but I'm sure he's got other
106:36 

106:36 things to do on, you know, throughout
106:38 

106:38 his day.
106:42 

106:42 I hope that was Matt laughing. I saw a
106:44 

106:44 little emoji.
106:47 

106:47 >> Sorry. Th this is great context. I I
106:51 

106:51 think it just helps build, you know, the
106:53 

106:53 understanding of of what, you know, the
106:56 

106:56 the idea is and what's needed here.
106:59 

106:59 Certainly I think we have a role to
107:03 

107:03 provide you know as you know to to
107:06 

107:06 collaborate and get the right people
107:09 

107:09 involved and at the table and so we've
107:12 

107:12 got you know
107:14 

107:14 association members represented as
107:18 

107:18 the core DDSG membership
107:22 

107:22 that we can go out to and you know
107:25 

107:25 dialogue with if those individuals are
107:28 

107:28 the person
107:30 

107:30 to
107:32 

107:32 have that leadership role in the AG or
107:35 

107:35 not, I think remains an open question.
107:38 

107:38 We'll just have to have that dialogue
107:40 

107:40 with those associations
107:43 

107:43 on who they want to have on the IG. It
107:46 

107:46 may be the same person that they have
107:48 

107:48 represented on the DDSG
107:51 

107:51 um perhaps or perhaps not. But then that
107:54 

107:54 provides the communication mechanism not
107:57 

107:57 only through the DDSG and through that
107:59 

107:59 association
108:01 

108:01 but then whenever the other more
108:03 

108:03 targeted you know product inputs are
108:06 

108:06 needed then they've got mechanisms
108:10 

108:10 beyond even what the DDSG would to go to
108:13 

108:13 their expertise of their members that
108:16 

108:16 would be able to represent them you know
108:19 

108:19 as an association on those individual
108:22 

108:22 product review and inputs as well. And
108:24 

108:24 so it it helps kind of broaden the net,
108:27 

108:27 if you will, by us, I think, starting
108:29 

108:29 there with that coordination
108:32 

108:32 on on those association members.
108:35 

108:35 >> Well, and I and I think
108:37 

108:37 >> to to build on that, right, we have, you
108:41 

108:41 know, we broke it into eight groups of
108:43 

108:43 disciplines, right? And then there's
108:44 

108:44 bridge, right, as well, right? That's
108:46 

108:46 already been going on.
108:49 

108:49 We don't necessarily expect to have a
108:51 

108:51 representative from each in the IG from
108:54 

108:54 each of those areas, right? But the
108:57 

108:57 person needs to know who from my group,
109:02 

109:02 right? ACC, ARPA, whoever can represent
109:06 

109:06 us. It may be some of them have one
109:07 

109:07 person representing three of those
109:09 

109:09 different disciplines or functional
109:11 

109:11 areas of of work or they might need one
109:14 

109:14 for each, right? depending on on you
109:17 

109:17 know I can imagine pipe builders might
109:19 

109:19 might want to bring somebody into into
109:22 

109:22 the game at the I a level right um you
109:25 

109:25 know that type of thing and you know the
109:27 

109:27 different paving associations right um
109:30 

109:30 there's overlap right um between th
109:33 

109:33 those that develop do paving and those
109:35 

109:35 that you know or concrete for bridges
109:37 

109:37 but they're not the same right um
109:41 

109:41 overlapping materials I mean is what I
109:42 

109:42 meant to say so like that's what we're
109:44 

109:44 talking about like who do you know, we
109:46 

109:46 need to really establish those IG
109:48 

109:48 members that can pull in those people to
109:51 

109:51 pull that that that are going to work on
109:54 

109:54 those technical working groups um as we
109:57 

109:57 dive into the weeds a little bit more,
109:59 

109:59 right? To get feedback, past products,
110:01 

110:01 whatever.
110:03 

110:03 >> Yeah. Yeah. Thanks for that, John.
110:05 

110:05 That's that's a good point. I I mean, I
110:08 

110:08 see it a little bit even like, you know,
110:09 

110:09 how we structured the DDSG membership.
110:12 

110:12 You know, we have some people that are
110:14 

110:14 down in the weeds at a very specific
110:17 

110:17 topic and we also have some, you know,
110:21 

110:21 much higher level leadership within a
110:23 

110:23 state agency that, you know, they have a
110:27 

110:27 bunch of other counterparts or employees
110:29 

110:29 that are down in the weeds, but we were
110:32 

110:32 looking for them to have that higher
110:33 

110:33 level kind of leadership perspective and
110:35 

110:35 be able to kind of, you know, show how
110:37 

110:37 these pieces fit together and how it's
110:39 

110:39 important for them at a leadership
110:42 

110:42 level, not just at, you know, one
110:44 

110:44 specific technical working level. Um, so
110:48 

110:48 there's there's that role as well, which
110:50 

110:50 I think is an excellent, you know, item
110:52 

110:52 to highlight because it's not always
110:54 

110:54 somebody who who has, you know, a
110:57 

110:57 specific, you know, talent on whether
110:60 

111:00 it's structures or, you know, pavement
111:03 

111:03 materials, but but we're talking about
111:05 

111:05 the more holistic. There's a lot of
111:07 

111:07 pieces in here that are going to need a
111:09 

111:09 lot of expertise. We just need to
111:12 

111:12 identify some people for the I A that
111:15 

111:15 can represent their industry, their
111:18 

111:18 association, and be able to go out and
111:21 

111:21 then, you know, shake the trees, so to
111:24 

111:24 speak, to get other people involved to
111:27 

111:27 help at the working level on some very
111:29 

111:29 detailed aspects
111:31 

111:31 >> and then and then be the person that
111:33 

111:33 that trusts and knows that that person
111:35 

111:35 is going to represent their
111:36 

111:36 organization,
111:38 

111:38 right? um and be a good solid
111:40 

111:40 representative in that area, right?
111:43 

111:43 >> Yeah. Yeah. Yeah. If you're if you're
111:45 

111:45 supportive of digital delivery and then
111:47 

111:47 that person comes in saying that you
111:50 

111:50 guys aren't doing the right things, then
111:52 

111:52 that's not helpful, right?
112:04 

112:04 We'll see. Um, I know we got some of the
112:08 

112:08 DDSG members, you know, online. Does
112:10 

112:10 anybody have any specific questions
112:14 

112:14 from, you know, from the perspective of
112:17 

112:17 starting this dialogue? Um and you know
112:21 

112:21 we can certainly Roger and I as a
112:24 

112:24 followup action you know bring this up
112:27 

112:27 specifically to all the DDSG members
112:29 

112:29 about their involvement in this I a
112:34 

112:34 want to identify somebody else to
112:36 

112:36 represent you know their either their
112:39 

112:39 agency or their industry or association
112:43 

112:43 there are you know I'm sure there are
112:46 

112:46 others that as have already been
112:49 

112:49 mentioned other associations that we
112:51 

112:51 don't have a DDSG member but um would be
112:55 

112:55 pertinent on the I AG as well to kind of
112:58 

112:58 broaden the net
113:00 

113:00 but we certainly want any dialogue or
113:02 

113:02 questions from any of the other DDSG
113:05 

113:05 members online.
113:10 

113:10 >> Hey Matt and uh John, good to see you
113:13 

113:13 again by the way. um
113:16 

113:16 you know your discussion there about
113:18 

113:18 kind of that leadership perspective um
113:20 

113:20 you know I have some background in this
113:23 

113:23 uh but obviously not the technical
113:25 

113:25 background for many many years but what
113:28 

113:28 I would like is as I'm um you know
113:31 

113:31 working with this group and working with
113:32 

113:32 the other ASHTO task force
113:35 

113:35 please let me know specifically what are
113:37 

113:37 the messages that you need me to to help
113:40 

113:40 carry um I get that this is this is big
113:44 

113:44 and there's a lot of pieces and there's
113:46 

113:46 a lot of uh entities that that that
113:50 

113:50 touch this issue and and maybe you know
113:52 

113:52 subject matter experts but if there's
113:55 

113:55 anything specific that I can bring to my
113:58 

113:58 counterparts and other leadership and I
113:60 

113:60 know um Carrie's not on right now but
114:03 

114:03 she's the on the chief engineers with
114:05 

114:05 ASHTTO as well that can help carry those
114:07 

114:07 messages uh please make sure that those
114:10 

114:10 are specifically conveyed
114:13 

114:13 I think Brandon, I'm glad you you uh
114:15 

114:15 brought that up. You know, like
114:17 

114:17 >> the you know, the Michigan
114:18 

114:18 Infrastructure Council, right, back back
114:19 

114:19 when that was being formed, right? I I
114:22 

114:22 kind of imagine this being that at a
114:25 

114:25 national level, right?
114:26 

114:26 >> How do we bring in the right pieces and
114:28 

114:28 parts to make sure that we're we're
114:30 

114:30 providing the input and the influence um
114:33 

114:33 we're needed uh to move these things
114:35 

114:35 forward? So, but I don't know if that
114:37 

114:37 resonates with you, but
114:39 

114:39 >> yeah, it does. And and John, you
114:42 

114:42 remember back in the day we struggled
114:43 

114:43 because I was in design with John and
114:46 

114:46 and we were all gung-ho, but we had
114:48 

114:48 trouble getting other parts of the
114:50 

114:50 organization engaged and involved. So I
114:53 

114:53 just see it very similar to that only on
114:55 

114:55 a on a national scale.
114:57 

114:57 >> Right. Exactly.
115:03 

115:03 >> Yeah. Thanks for that, Brad. I think
115:05 

115:05 that goes to the what we were talking
115:07 

115:07 about a little bit earlier about, you
115:10 

115:10 know, what what are the more specific
115:13 

115:13 requirements and when do they occur
115:15 

115:15 because I think from looking at this the
115:18 

115:18 the two poolled funds have different
115:19 

115:19 things going on at different times that
115:22 

115:22 you would be seeking advice on. So maybe
115:26 

115:26 some way that we can keep some kind of a
115:28 

115:28 good track of that in one place or in
115:31 

115:31 one way would help with how the DDSG
115:35 

115:35 could work with our membership to ensure
115:38 

115:38 the poolled funds are getting what
115:40 

115:40 they're looking for and uh at any
115:44 

115:44 particular time,
115:47 

115:47 >> right?
115:53 

115:53 And
115:55 

115:55 for for my clarity, the I A whoever that
115:60 

116:00 person sitting on that,
116:04 

116:04 they're going to be involved in both
116:07 

116:07 pulled funds
116:09 

116:09 efforts and information and discussion.
116:12 

116:12 So the is that correct? That was the
116:16 

116:16 vision, right?
116:18 

116:18 >> It is the intent that this I AG would be
116:20 

116:20 inclusive of both pulled funds. So
116:22 

116:22 information would funnel through there
116:25 

116:25 for both pulled funds.
116:27 

116:27 >> Yeah. So similar to today in those kind
116:31 

116:31 of discussions or meetings or
116:33 

116:33 engagements, it would be a collaborative
116:36 

116:36 the pulled funds together to kind of
116:38 

116:38 leverage the time and not have separate
116:41 

116:41 meetings. Correct.
116:42 

116:42 >> Corre correct. Yep.
116:43 

116:43 >> Yeah.
116:44 

116:44 >> Why schedule two meetings when you can
116:45 

116:45 schedule one? You know.
116:47 

116:47 >> Yeah. Yeah. Yeah.
116:48 

116:48 >> And then it say it communicates the same
116:50 

116:50 message and the same understanding, you
116:52 

116:52 know, and like we noted earlier,
116:54 

116:54 there'll be a few different separations.
116:56 

116:56 The IG, you know, like on the bridge
116:57 

116:57 side, we're going to have NSBA because
116:59 

116:59 they have task group 15 doing digital
117:00 

117:00 delivery. Now, members of task group 15
117:03 

117:03 will be in the technical working group.
117:04 

117:04 You know, uh NSBA is very eager to get
117:06 

117:06 digital delivery moving. Um the same
117:09 

117:09 with NCBC. you know they have a
117:11 

117:11 technical delivery group that's been
117:13 

117:13 digital delivery group that's been
117:15 

117:15 working on this stuff but we need high
117:16 

117:16 level members participating at that you
117:19 

117:19 know I'm not sure we need to get too
117:21 

117:21 elaborate on this you know I I think
117:23 

117:23 we're you know several meetings a year
117:25 

117:25 communicating what's being done what's
117:27 

117:27 national standards and where we're going
117:29 

117:29 is good for that industry advisory group
117:31 

117:31 now we start looking at the technical
117:32 

117:32 working groups like uh uh Jim Mayhew's
117:35 

117:35 presentation from Monday I thought that
117:37 

117:37 was awesome what he's doing with IFC you
117:39 

117:39 know I'm hoping he's sharing that
117:40 

117:40 information with BIM for infrastructure
117:42 

117:42 and and you know incorporating some of
117:44 

117:44 the IFC work that that he's looked at
117:47 

117:47 but you know to me that's more technical
117:48 

117:48 so you know like uh this meeting we had
117:50 

117:50 three separate meetings you know I think
117:53 

117:53 you could have you know one that's an
117:54 

117:54 industry advisory group and a couple
117:56 

117:56 more that are a little more technical
117:57 

117:57 but if you guys could collect all the
117:59 

117:59 stuff that you know all these ADCMS
118:01 

118:01 that's a huge investment by the FHWA
118:04 

118:04 it'd be nice communicating
118:06 

118:06 what are the national standards or open
118:08 

118:08 data standards that are being developed
118:09 

118:09 in these poolled in these poolled funds
118:11 

118:11 and how can they be shared and utilized
118:13 

118:13 by others. You know, I I think we have
118:16 

118:16 to be careful on how we do this, but a
118:19 

118:19 role of collecting that data and
118:21 

118:21 communicating it and sharing it would be
118:24 

118:24 beneficial. And I'm sure the FHWA has a
118:26 

118:26 effort on to try to communicate that
118:28 

118:28 stuff, but centralizing that with what
118:30 

118:30 the poolled funds are done. You know,
118:32 

118:32 ours are, you know, the BIM for Bridge
118:33 

118:33 is very focused on that IFC deliverable
118:36 

118:36 design and construction. Now, we're
118:37 

118:37 moving on to fabrication, hoping to get
118:38 

118:38 through as builts during this, you know,
118:40 

118:40 next work cycle. But you know getting
118:43 

118:43 into the there's to you know we have a
118:46 

118:46 wide spectrum here of high level people
118:47 

118:47 and more technical people and I think we
118:51 

118:51 need to separate separate not that the
118:53 

118:53 groups can't play along but we can't be
118:56 

118:56 consuming too much of people's times in
118:58 

118:58 each of these groups. So I think if
118:60 

118:60 we're more focused on that message and
119:01 

119:01 who needs to hear what message it'll be
119:03 

119:03 beneficial.
119:07 

119:07 Yeah, I I think a lot of this makes
119:12 

119:12 sense um from my perspective. I I'm
119:15 

119:15 definitely not in the weeds. Um but I
119:19 

119:19 mean that you know the role that we can
119:21 

119:21 facilitate is certainly that
119:22 

119:22 collaboration and identifying the right
119:25 

119:25 people
119:26 

119:26 um to to be involved with with you know
119:30 

119:30 that leadership group and it may be the
119:33 

119:33 same people in certain areas as those on
119:36 

119:36 the DDSG which provides a little bit
119:39 

119:39 more consistency and easier dialogue.
119:45 

119:45 The I guess the other would be there is
119:48 

119:48 a potential that as other
119:51 

119:51 pulled funds come online that those
119:53 

119:53 would be incorporated in this as well.
119:56 

119:56 Correct
119:60 

119:60 or no?
120:01 

120:01 >> I would think so. Jim, have you given
120:03 

120:03 that any thought?
120:04 

120:04 >> Yep. I have a meeting with Kyle and
120:06 

120:06 we're going to discuss this on Monday.
120:08 

120:08 Kyle Clute, he's the one that does the
120:09 

120:09 financing and, you know, submits the
120:12 

120:12 proposals. I'm the technical lead for
120:14 

120:14 it, but the software certification file
120:16 

120:16 validation poolled fund. I sent out a
120:18 

120:18 poll like I said I would after Monday to
120:21 

120:21 get you know our kickoff meeting going.
120:23 

120:23 I anticipate that will be part of BIM
120:25 

120:25 week along with BIM for bridge BIM for
120:27 

120:27 infra software certification file
120:29 

120:29 validation and they will become part of
120:33 

120:33 this
120:37 

120:37 and then how like I guess how broad of a
120:40 

120:40 net for other pulled funds or other
120:43 

120:43 efforts like you know like the UAS
120:45 

120:45 pulled fund that's coming up
120:49 

120:49 um or some of those areas that kind of
120:51 

120:51 you know feed into digital delivery.
120:54 

120:54 Would would those be of interest to be
120:57 

120:57 part of this as well or does that get it
120:60 

120:60 too broad?
121:00 

121:00 >> Yeah, I think we would have to um
121:02 

121:02 consider each one on a case- by case
121:04 

121:04 basis. It is important to keep the I A
121:06 

121:06 small um you know because we want to
121:09 

121:09 have that open dialogue and if it's if
121:11 

121:11 it grows too big and too broad you know
121:14 

121:14 it loses its its purpose. Um yeah I
121:17 

121:17 think we would consider things like that
121:19 

121:19 on a on an as needed basis.
121:22 

121:22 I I think there's also um some benefit
121:26 

121:26 we'll get from time because I think how
121:31 

121:31 much needs to be DDSG versus I AG and
121:36 

121:36 when I think just doing this for a while
121:38 

121:38 will clarify some of that. I think we
121:41 

121:41 maybe have a framework to go forward
121:43 

121:43 with but that could evolve a little bit.
121:46 

121:46 I've there's a couple comments been made
121:49 

121:49 on the mural and in the chat about, you
121:52 

121:52 know, just keeping things uh focused and
121:55 

121:55 not um going too far or not letting
121:59 

121:59 things creep. So, I think we'll figure
122:01 

122:01 that out as we go forward. I think we
122:04 

122:04 all have the overarching goal to not
122:07 

122:07 waste people's time and not ask for the
122:10 

122:10 same thing
122:11 

122:11 >> in two different places and everything.
122:13 

122:13 So if we keep that in mind, I think
122:16 

122:16 that'll help us as we go forward also.
122:20 

122:20 >> Well, and I think from the standpoint of
122:22 

122:22 some of you as we get into some of these
122:24 

122:24 other disciplines and functional areas,
122:25 

122:25 right? They start to get represented by
122:28 

122:28 different committees and subcommittees
122:29 

122:29 in in in Ashtto, right? Um and the the
122:34 

122:34 joint technical committee electronic
122:36 

122:36 engineering standards and jan have cross
122:39 

122:39 representation from some of those
122:40 

122:40 committees. So, I think really leaning
122:43 

122:43 into cross representation of those
122:46 

122:46 committees in the poolled funds um to
122:50 

122:50 get that input as well as focusing on
122:53 

122:53 the ones that may not be represented in
122:55 

122:55 those joint committees um to make sure
122:58 

122:58 we're getting that particular piece of
122:60 

122:60 information or that that insight might
123:02 

123:02 might be a way to go
123:05 

123:05 instead of going and bringing in another
123:07 

123:07 um group, right? Um, just a thought. I'm
123:12 

123:12 just thinking about when you start
123:13 

123:13 getting into traffic operations.
123:16 

123:16 >> We're not getting into the weeds of all
123:17 

123:17 the data that gets passed between uh
123:19 

123:19 devices because there's a whole another
123:21 

123:21 standard getting developed through some
123:22 

123:22 other pulled funds on that, but we are
123:25 

123:25 aware of those and we're trying to make
123:26 

123:26 sure that what we create can connect to
123:28 

123:28 those. Right? So talking about scope
123:31 

123:31 creep, we're not going to go and engage
123:32 

123:32 with them uh directly as we develop
123:35 

123:35 these, but they'll be able hopefully to
123:37 

123:37 um feed their information in, right? So
123:40 

123:40 um just to follow up on that thought, I
123:44 

123:44 think it's important to be mindful of
123:45 

123:45 that.
123:50 

123:50 >> Yeah, that's a good point, John. I like
123:52 

123:52 that. I think you know this what you
123:54 

123:54 guys need is pretty clear for your two
123:57 

123:57 pool phones and keeping an eye on that
123:60 

124:00 as we go forward to not overwhelm it
124:04 

124:04 with other things is good and maybe the
124:06 

124:06 DDSG is broader at that level to provide
124:11 

124:11 one coordination point anyway
124:15 

124:15 when we started we had uh different
124:17 

124:17 liaison right um and those were state
124:20 

124:20 DOT representatives and That's how we're
124:22 

124:22 engaging with industry and making sure
124:25 

124:25 that we're getting the word out. Um that
124:26 

124:26 that drove us engaging with um the TRB
124:29 

124:29 survey and geodetic committee, right, to
124:33 

124:33 understand that we're we're addressing
124:34 

124:34 the needs of the new uh reference
124:37 

124:37 system, right, in the structure that we
124:39 

124:39 create. Um further followup is
124:41 

124:41 necessary. Is that go through the IG or
124:44 

124:44 is that we have a technical working
124:46 

124:46 group with them to to iron that out
124:47 

124:47 because there isn't really an overall
124:50 

124:50 establishment on that, right? And that's
124:52 

124:52 probably the small group. We already
124:53 

124:53 know they exist and we can go engage
124:55 

124:55 with them on on that specific need,
124:57 

124:57 right? Um just an example,
125:04 

125:04 but this is more formalizing a lot of
125:06 

125:06 that to make sure that as we roll these
125:07 

125:07 out, there's been input and buying from
125:11 

125:11 the different industry groups. So
125:21 

125:21 >> yeah, I mean we we have some inherent
125:23 

125:23 overlap already in the DDSG members of
125:27 

125:27 those that you know serve on the you
125:30 

125:30 know some of the ASHTO uh committees
125:33 

125:33 that you've mentioned and you know
125:36 

125:36 certainly there are
125:39 

125:39 other state agencies
125:43 

125:43 represented on the DDSG that has
125:45 

125:45 somebody within their agency that you
125:47 

125:47 know represents some facet of an ASHTO
125:50 

125:50 committee as well. So,
125:52 

125:52 um the coordination piece I think is
125:54 

125:54 where we're trying to get to on all
125:56 

125:56 these things is so kind of everybody's
125:58 

125:58 on the same page. I I think so what let
126:03 

126:03 me see if I'm interpreting and my action
126:05 

126:05 item or the DDSG's action item is for us
126:09 

126:09 to go back to our DDSG core membership
126:13 

126:13 and identify those
126:16 

126:16 that we could leverage on the industry
126:20 

126:20 advisory group and if it is in fact
126:24 

126:24 going to be the the same person that's
126:27 

126:27 represented on the DDSG or somebody else
126:30 

126:30 to represent their association or agency
126:34 

126:34 and get a a listing of those that would
126:37 

126:37 have an interest in being part of this
126:40 

126:40 higher level. Hey, let's talk about the
126:42 

126:42 issues. Let's talk about what the pulled
126:44 

126:44 funds delivering. Um what other
126:48 

126:48 resources you know do you have in your
126:51 

126:51 association to help with some of the
126:53 

126:53 more detailed uh review of products
126:57 

126:57 because of their expertise but have at
126:59 

126:59 least a central person identified that
127:02 

127:02 can help those dialogues further down uh
127:05 

127:05 downstream.
127:06 

127:06 Is is that is that the right action item
127:09 

127:09 that I'm capturing?
127:19 

127:19 I think so. Matt, I think there's
127:22 

127:22 >> Oh, yeah.
127:22 

127:22 >> So, here, let me uh
127:24 

127:24 >> Oh, Julie, you're gonna You got
127:26 

127:26 something?
127:26 

127:26 >> Yeah, I was starting to talk while I was
127:27 

127:27 on mute. Um, I was just going to
127:29 

127:29 mention, Matt, in response to your
127:31 

127:31 question, uh, that we are planning to
127:34 

127:34 have a meeting between the poolled fund
127:37 

127:37 leadership and DDSG, a small group
127:39 

127:39 meeting to kind of hash out some of
127:41 

127:41 those details. So I think you're on the
127:42 

127:42 right track, but we're planning to have
127:44 

127:44 that discussion um in the near future.
127:47 

127:47 >> Okay, perfect.
127:49 

127:49 >> So
127:51 

127:51 let's just
127:52 

127:52 >> I mean I really think the poolled funds
127:54 

127:54 need to identify their industry advisory
127:56 

127:56 groups. You know, I I'm not sure this is
127:58 

127:58 a role for the FHWA.
128:01 

128:01 You know, from the standpoint, you know,
128:03 

128:03 we've already done have gone through
128:06 

128:06 this effort on some things. You know, I
128:09 

128:09 the poolled funds know who they need on
128:11 

128:11 their industry advisor group. There's
128:13 

128:13 going to be a lot of crossover with AGC,
128:15 

128:15 ACEC, and ARPA, but there's going to be
128:19 

128:19 specific needs to each one. And so I
128:24 

128:24 I guess I don't want to lose focus on
128:26 

128:26 what we're doing here. You know, I see
128:28 

128:28 the digital delivery stakeholder group
128:29 

128:29 definitely being needed. you know, when
128:31 

128:31 I communicated and solicited my new the
128:33 

128:33 upcoming poolled fund for software
128:35 

128:35 certification file validation, um, you
128:38 

128:38 know, I reached out to existing poolled
128:40 

128:40 fund members. There's a lot of states
128:41 

128:41 that are not in these pulled funds and
128:43 

128:43 communicating and sharing that message
128:45 

128:45 with them is invaluable. I mean, they
128:47 

128:47 need they need to know what's out there.
128:49 

128:49 So, I I I
128:51 

128:51 I guess I don't see this digital
128:53 

128:53 delivery stakeholder group taking over
128:55 

128:55 the industry advisory group. You know,
128:57 

128:57 there's some coordination effort. I
128:59 

128:59 really see you guys sharing information
129:00 

129:00 and communicating out what's needed. Um
129:03 

129:03 I'm going to go back to governance not
129:04 

129:04 to steal Trish's thunder but you know
129:06 

129:06 governance is needed. TPFs are not
129:08 

129:08 ASHTTO you know we have a US bridge data
129:11 

129:11 dictionary that we are using as part of
129:13 

129:13 BIM for bridge that is not a national
129:15 

129:15 publication but we need those ASHTTO
129:16 

129:16 endorsements. So communicating to the
129:19 

129:19 upper level management why that
129:21 

129:21 information is needed there. You know,
129:23 

129:23 there's a role there and that's really
129:25 

129:25 needs to happen to get these pulled
129:27 

129:27 funds deliverables into national
129:29 

129:29 standards that are ASHTO endorsed and
129:31 

129:31 there's a lot of challenges associated
129:33 

129:33 with that. But, you know, I I think we
129:36 

129:36 need to have a discussion maybe with the
129:39 

129:39 poolled funds, you know, like Julie was
129:40 

129:40 doning leadership and exactly what we
129:42 

129:42 need and how to support and coordinate
129:44 

129:44 this effort because I really see DD DDSG
129:47 

129:47 being needed. I I just think we need to
129:49 

129:49 get on the same wavelength.
129:54 

129:54 Yeah, that's that's I mean that's that's
129:56 

129:56 all perfectly understandable. I'm I'm
129:59 

129:59 gonna I'm gonna wind back my action item
130:02 

130:02 or our action item and
130:06 

130:06 when
130:08 

130:08 we meet and have that meeting between
130:11 

130:11 the pull fund executive and the DDSG
130:17 

130:17 um and kind of work through those
130:18 

130:18 details. then we can formulate I think
130:20 

130:20 the appropriate action moving forward
130:22 

130:22 then uh Roger
130:26 

130:26 >> got it
130:33 

130:33 >> I just wanted to make sure I wasn't
130:34 

130:34 missing I guess an opportunity for us to
130:37 

130:37 you know build some momentum but I also
130:41 

130:41 understand the perspectives and you you
130:43 

130:43 know want to make sure we're all on the
130:45 

130:45 same page so I don't want to rush to an
130:48 

130:48 action an item that's counterproductive
130:50 

130:50 to that.
130:52 

130:52 >> Oh, I wouldn't say it's
130:53 

130:53 counterproductive. I just want to make
130:54 

130:54 sure it aligns and supports and doesn't
130:57 

130:57 duplicate.
130:59 

130:59 >> Yeah. Yeah. No, very understandable. I
131:02 

131:02 mean, we're we're here to provide
131:04 

131:04 resources and to help and we don't we
131:05 

131:05 don't want to be a barrier hindrance.
131:14 

131:14 any other
131:18 

131:18 dialogue from the members or online? I
131:21 

131:21 know
131:24 

131:24 um there are some comments coming in.
131:27 

131:27 I'll open up maybe for a couple other
131:29 

131:29 just like general. So there was a
131:31 

131:31 question if anybody knew of uh dos that
131:35 

131:35 are incorporating geotech foundation
131:37 

131:37 subsurface information in BIM. Um, if
131:42 

131:42 you are aware or you are a state that's
131:44 

131:44 doing that, maybe you can just throw the
131:47 

131:47 the state name in the chat in response
131:49 

131:49 to that one. Um, just for awareness.
131:54 

131:54 >> That did get answered some in the Q&A by
131:57 

131:57 John. Thank
131:59 

131:59 >> Oh, I I completely missed the Q&A. Well,
132:02 

132:02 I I think there's still a need to
132:04 

132:04 revisit and figure out if there are
132:06 

132:06 states doing that because I don't know
132:07 

132:07 that they, you know, from my
132:08 

132:08 recollection, a lot of states are still
132:11 

132:11 assessing how to leverage those tools
132:14 

132:14 um because of the revamp of a lot of
132:17 

132:17 them over the last 5 day years. Um
132:21 

132:21 but I and I think I what I pointed out
132:23 

132:23 right is admittedly so aren't the only
132:26 

132:26 geotech information that needs to be
132:28 

132:28 passed through the life cycle of an
132:29 

132:29 asset, right? Um but with the BIM for
132:32 

132:32 infrastructure pool fund that's really
132:34 

132:34 what we focused on with the geotechnical
132:36 

132:36 piece of the information mainly to make
132:38 

132:38 an a connection for more engagement more
132:42 

132:42 interaction um from geotechnical right
132:45 

132:45 make those touch points for further
132:46 

132:46 extension
132:48 

132:48 of the standard so I can get something
132:51 

132:51 out there and get a structure for some
132:52 

132:52 of these things uh it goes back to what
132:55 

132:55 I said earlier about the the traffic
132:57 

132:57 management systems right we didn't get
132:59 

132:59 into all the equipment, all the
133:01 

133:01 information passing in between all that
133:02 

133:02 equipment because there's already
133:03 

133:03 standards getting developed for that.
133:05 

133:05 Um, we just need to make sure that we
133:07 

133:07 can interact with that, right, as a
133:09 

133:09 touch point.
133:18 

133:18 And uh yeah, Matt Miller from Iowa just
133:21 

133:21 just stating that identifying some of
133:24 

133:24 the potential crosswalks would
133:27 

133:27 definitely be valuable and goes into a
133:29 

133:29 lot more detail of
133:32 

133:32 some of the operational things and
133:34 

133:34 things of need. Always appreciate uh
133:38 

133:38 Matt Miller's comments and information.
133:41 

133:41 Uh and Trisha, Trisha's involved in so
133:44 

133:44 many things. when she gets a chance to
133:46 

133:46 engage with me, I always learn something
133:48 

133:48 new.
133:49 

133:49 >> Yeah. I guess just to kind of elaborate
133:51 

133:51 on that, you know, uh as as I mentioned
133:54 

133:54 it to to our operations folks with the
133:58 

133:58 >> with the corridors, um you know, BIM and
134:02 

134:02 and this digital delivery is going to
134:04 

134:04 offer access to asset data that we just
134:07 

134:07 really haven't had up up until, you
134:10 

134:10 know, this is starting to come out. Uh
134:13 

134:13 but what we've seen in all of our event
134:15 

134:15 data is even with data standards,
134:17 

134:17 there's huge deviations state-to-state
134:20 

134:20 and and I expect we'll probably see some
134:24 

134:24 of that going forward with some of these
134:26 

134:26 uh solutions for for at least a while.
134:28 

134:28 But I think drawing attention to what
134:31 

134:31 are what is that specific asset data
134:34 

134:34 that's going to help me as far as the
134:36 

134:36 public facing view uh with operations, I
134:39 

134:39 think is uh is pretty important. Um, we
134:43 

134:43 went through this recently where we had
134:45 

134:45 uh license plate readers that people
134:47 

134:47 were putting in our rideway and we had
134:49 

134:49 to assemble a map recently and the
134:51 

134:51 permitting process is still kind of a
134:53 

134:53 paper hand in thing and people were
134:56 

134:56 like, "Hey, we need a map of where all
134:57 

134:57 these license plate readers are and it
135:01 

135:01 it took a while. Somebody had to spend
135:03 

135:03 their whole weekend trying to map out
135:05 

135:05 all these different locations." Uh so
135:08 

135:08 you know we still got this sort of
135:09 

135:09 historical way that we've been doing
135:11 

135:11 things but I think everybody's looking
135:13 

135:13 forward to this thought that this data
135:16 

135:16 will be usable uh beyond its its
135:19 

135:19 original intention. So thank you very
135:22 

135:22 much.
135:23 

135:23 >> Yeah. No good good point. I I know I've
135:27 

135:27 heard heard it stated multiple times and
135:29 

135:29 and I'll I'll restate it, but you know,
135:31 

135:31 for example, in in not too distant uh
135:35 

135:35 history when there was the investigation
135:38 

135:38 on the entryments
135:41 

135:41 uh for the guide rail or guardrail
135:43 

135:43 depending on which state you live in. Um
135:47 

135:47 uh you know and and yeah you know most
135:49 

135:49 people had to spend a lot of time and
135:51 

135:51 effort to go out and identify where
135:53 

135:53 those were installed and where they were
135:55 

135:55 located because there wasn't a good way
135:58 

135:58 that you know the promise of what we're
136:00 

136:00 discussing today would have made that
136:03 

136:03 much easier to be able to respond to.
136:06 

136:06 I think in that example, a lot of a lot
136:08 

136:08 of agencies knew how many
136:11 

136:11 um but they didn't know which ones were
136:12 

136:12 still in good condition and where where
136:14 

136:14 exactly they were,
136:16 

136:16 right?
136:17 

136:17 >> Yep. Yep.
136:26 

136:26 >> Okay. Um
136:29 

136:29 seems like the dialogues
136:32 

136:32 slowed a little bit. Uh
136:38 

136:38 we'll reconvene I guess um with the
136:43 

136:43 pulled funds here uh in short order and
136:47 

136:47 circle back with the DDSG membership uh
136:52 

136:52 with that strategy.
136:54 

136:54 And certainly there's again a lot of uh
136:59 

136:59 transportation pulled fund efforts going
137:01 

137:01 on in the ones that exist in the ones
137:04 

137:04 that are coming online. So um we'll
137:06 

137:06 continue to have that engagement um
137:10 

137:10 as we move forward uh with our
137:12 

137:12 additional agenda items. Let me
137:17 

137:17 turn my screen up
137:21 

137:21 and we will
137:27 

137:27 so we have um we will
137:31 

137:31 not hear anything else to discuss.
137:33 

137:33 Roger, I think we can wrap up and give
137:35 

137:35 some people a little bit of time back. I
137:37 

137:37 really do appreciate the engagement and
137:40 

137:40 the dialogue. Uh and
137:44 

137:44 um we will follow up on the Delaware
137:48 

137:48 presentation. We hope to get get their
137:50 

137:50 presentation uh provided. Uh I hope
137:54 

137:54 Cassidy uh gets well soon. Um there will
137:58 

137:58 be other ADCMS projects again from the
138:01 

138:01 advanced digital construction management
138:03 

138:03 systems grants. Uh I can't speak for
138:07 

138:07 leadership on the status of those
138:09 

138:09 efforts currently. So we'll likely hear
138:12 

138:12 more information uh coming up in short
138:15 

138:15 order um about any new opportunities as
138:19 

138:19 well. But we'll follow up on those
138:22 

138:22 projects that have been initiated and
138:24 

138:24 started
138:26 

138:26 um and some additional research. Uh
138:29 

138:29 we'll just again highlight the the mural
138:31 

138:31 board uh one last time is it will be
138:34 

138:34 open and available and you know please
138:37 

138:37 provide your comments or questions or um
138:42 

138:42 feedback. Uh if you do have any schedule
138:47 

138:47 items that you're aware of that you can
138:49 

138:49 help us crowdsource and contribute on
138:51 

138:51 the mural board uh that would be much
138:54 

138:54 appreciated. We are, you know, we did
138:56 

138:56 start to assemble uh those there, but
138:58 

138:58 we've had others added here in the last
139:01 

139:01 couple days. Much appreciated. Um so,
139:05 

139:05 please add those items. We uh look to
139:08 

139:08 leverage that information quite
139:10 

139:10 extensively for scheduling moving
139:11 

139:11 forward.
139:14 

139:14 You know, Matt, maybe to that point, we
139:16 

139:16 can if you do have any feelings about
139:19 

139:19 those events that would be good for the
139:21 

139:21 DDSG to potentially colllocate with or
139:25 

139:25 collaborate with, we'd welcome any
139:28 

139:28 comments people have on that as we look
139:32 

139:32 to schedule our next in-person meeting
139:35 

139:35 um later in the year. So that's part of
139:38 

139:38 the reason for having this schedule of
139:41 

139:41 events is to help us with that. And if
139:43 

139:43 you have any thoughts, you want to drop
139:45 

139:45 them on the mural there next to the
139:47 

139:47 schedule, that would be welcome.
139:54 

139:54 >> Yeah,
139:55 

139:55 >> maybe. Yeah, you're going there. Good.
139:57 

139:57 >> Yeah, the So we we do have the next
140:00 

140:00 meeting three that is scheduled. Um we
140:04 

140:04 are partnering up with ASHTTO in their
140:07 

140:07 GI GIST
140:10 

140:10 uh annual conference that's being held
140:12 

140:12 this year in Chicago. Um again as a
140:16 

140:16 reminder we do have that information
140:19 

140:19 posted on the DDSG hub. Um, and if you
140:24 

140:24 don't have the direct web link, if you
140:26 

140:26 just search DDSG hub, but make sure you
140:29 

140:29 include the hub, uh, generally it's
140:31 

140:31 going to come up in the first kind of
140:33 

140:33 page of of items. There is a DSG hub
140:37 

140:37 that comes up. That's not us. It's DDSG
140:40 

140:40 hub. Um,
140:43 

140:43 uh,
140:45 

140:45 the, um, registration information there
140:48 

140:48 is as well. Uh, two separate ones. One
140:51 

140:51 for if you're going to be virtual,
140:53 

140:53 another one if you're going to be on
140:56 

140:56 site and you're looking to leverage the
140:59 

140:59 Ashtogis hotel room block. Um, our
141:04 

141:04 meeting is actually going to be at the
141:05 

141:05 hotel location, not at the GIST
141:09 

141:09 location, but the hotel location is the
141:11 

141:11 same and the room blocks the same. Um,
141:15 

141:15 this is our kind of preliminary working
141:17 

141:17 agenda. We are still fleshing out some
141:19 

141:19 of the details. uh on that. Um and we're
141:24 

141:24 always interested, you know, as a
141:26 

141:26 community, what is of interest to you,
141:29 

141:29 uh what kind of things you want to hear.
141:30 

141:30 So, uh if you want to contribute again
141:32 

141:32 in the mural board, um on what you think
141:36 

141:36 is important or what is, you know,
141:38 

141:38 emerging or urgent or, you know, part of
141:40 

141:40 that dialogue, uh for us to consider in
141:44 

141:44 future meetings and future agenda
141:46 

141:46 topics, feel free to add that. Our
141:49 

141:49 intent uh is to have again about four
141:53 

141:53 meetings per annual. Um the timing is
141:57 

141:57 going to be dependent on a lot of things
141:59 

141:59 including uh support contract extensions
142:02 

142:02 which are annual uh kind of funded um as
142:06 

142:06 we work through those business uh
142:08 

142:08 related details. The one in March being
142:11 

142:11 the hybrid combination on-site and
142:13 

142:13 virtual. The next one after that will be
142:15 

142:15 virtual only similar to this one. and
142:18 

142:18 then the next one after that again a
142:20 

142:20 hybrid. So we'll be alternating like
142:22 

142:22 that um into the future. Uh, you know,
142:27 

142:27 the only thing that's really kind of
142:28 

142:28 been brought up uh primarily as a target
142:31 

142:31 for our next in-person hybrid is again
142:35 

142:35 the I heap uh venue which unlike last
142:39 

142:39 year which was early October which
142:41 

142:41 created some difficulties
142:44 

142:44 um when it came for execution because of
142:46 

142:46 the budget conversation at a national
142:49 

142:49 level is later in the year this year. uh
142:52 

142:52 if we do end up uh getting consensus
142:55 

142:55 that that's the appropriate venue to
142:57 

142:57 target uh for that hybrid meeting that
142:60 

142:60 would be beginning of uh December and
143:02 

143:02 then you know the all virtual would be
143:05 

143:05 basically split between this March
143:08 

143:08 meeting and that December one but uh
143:10 

143:10 again we're we're trying to be very um
143:14 

143:14 proactive in in getting these things
143:16 

143:16 locked down uh and and how we're going
143:20 

143:20 to manage the schedule moving forward to
143:22 

143:22 to get that information out and travel
143:25 

143:25 plans uh as early as possible.
143:28 

143:28 Recognizing that sometimes there are
143:30 

143:30 challenges when we do partner up with
143:32 

143:32 other entities and logistics and you
143:35 

143:35 know conflict with their time and making
143:38 

143:38 sure we're not you know uh overbooking
143:40 

143:40 and or dual booking uh activities with
143:43 

143:43 the members as well. Um but uh your
143:46 

143:46 voice is important to us. Please
143:49 

143:49 collaborate with us in the mural board.
143:51 

143:51 Um we we do look at that information and
143:54 

143:54 digest it and try to make informed
143:56 

143:56 decisions with it as well.
144:01 

144:01 With that, uh Roger, I don't know if
144:03 

144:03 you've got any other parting words or uh
144:06 

144:06 words of wisdom like usual.
144:10 

144:10 >> No, no, this has been great. I think
144:11 

144:11 we've gotten a lot of good input. I feel
144:13 

144:13 like we've,
144:15 

144:15 you know, met the goal of this meeting
144:17 

144:17 to share and collaborate on things and
144:21 

144:21 to and to move into working on some
144:23 

144:23 things. I think between the the
144:26 

144:26 discussions with the uh ADCMS grants on
144:30 

144:30 on uh Monday and what we've talked about
144:33 

144:33 with the poolled funds on both Monday
144:35 

144:35 and today we've uh made some progress on
144:38 

144:38 how the DDSG can work with these
144:41 

144:41 different efforts and and that's our
144:44 

144:44 goal and you know this is really meant
144:46 

144:46 to be a resource for really for you out
144:50 

144:50 there in the community to use. So, it's
144:54 

144:54 great to get that input and work
144:57 

144:57 together and we'll keep at it and uh
144:59 

144:59 follow up on the items that come out of
145:01 

145:01 the meeting. So, and thanks and thanks
145:03 

145:03 to the people who presented for us over
145:06 

145:06 the last few days and shared. Um, and we
145:09 

145:09 encourage anyone who's interested in
145:12 

145:12 doing that in a future meeting to let us
145:15 

145:15 know. Um, you know, we want to keep the
145:17 

145:17 pulse on AMS grants and pool funds and
145:21 

145:21 things. So yeah, that's that's my
145:26 

145:26 closing.
145:28 

145:28 Matt, thanks.
145:29 

145:29 >> Yeah,
145:29 

145:29 >> it does look like we have a question
145:31 

145:31 from uh Gary Man
145:34 

145:34 or their hand is raised at least,
145:39 

145:39 >> Gary. Go ahead.
145:45 

145:45 Thank you. Um a question on the uh March
145:49 

145:49 19th and March 20th. Um, I see the uh
145:52 

145:52 events inside your uh on the web page
145:56 

145:56 and when I go into register on those, I
145:59 

145:59 don't see different registrations for
146:01 

146:01 inperson or virtual. It seems to be
146:04 

146:04 combined. Is is that okay if I register
146:07 

146:07 even though I'm only going to be
146:08 

146:08 virtual?
146:12 

146:12 >> Roger, you want to maybe you can bring
146:14 

146:14 up the
146:15 

146:15 >> Yeah, let me there see what we got
146:18 

146:18 going. Um,
146:20 

146:20 >> just so
146:21 

146:21 >> quickly if we could just
146:23 

146:23 >> make sure that we're all looking at the
146:25 

146:25 same thing, we might be able to resolve
146:28 

146:28 this pretty easily.
146:35 

146:35 >> Yeah, I think um we sent
146:40 

146:40 Yeah, I'm looking at the website. I I
146:42 

146:42 think um it only has the registration
146:47 

146:47 for the virtual meetings on our website.
146:51 

146:51 Um
146:55 

146:55 we sent out a communication about
146:57 

146:57 registering in person. Um
147:02 

147:02 so
147:04 

147:04 maybe that still needs to get clarified
147:07 

147:07 on the registration on site.
147:10 

147:10 Thought we had it there, but I'm not
147:11 

147:11 seeing it. Um,
147:18 

147:18 uh, oh, well, it's a little obscured. at
147:22 

147:22 the bottom of the description on each of
147:24 

147:24 the
147:26 

147:26 uh in-person registrations,
147:29 

147:29 there's a link to the the GIST
147:32 

147:32 conference website where you can
147:35 

147:35 register and they have a link there to
147:37 

147:37 register for just the
147:40 

147:40 um uh DDSG meeting. So, we may need to
147:46 

147:46 make that a little clearer on our web
147:48 

147:48 page. uh but it is under registration.
147:52 

147:52 It will direct you to the Ashtto site.
147:56 

147:56 If you register there then you can um uh
148:02 

148:02 get the registration for just the DDSG.
148:07 

148:07 Um
148:11 

148:11 >> Roger, do you want to share your screen
148:13 

148:13 so that people can see what you're
148:14 

148:14 referencing?
148:16 

148:16 >> I can. I'm not sure it's going to be a
148:18 

148:18 conclusive answer, but um let me go
148:21 

148:21 ahead and share
148:23 

148:23 um
148:25 

148:25 let's go back.
148:29 

148:29 I know when we looked at this before,
148:31 

148:31 there was the one link, you know,
148:33 

148:33 basically it was just virtual. The other
148:35 

148:35 one, it gave you if you if you wanted
148:38 

148:38 the room block information from from
148:41 

148:41 Ashtto because you were going to be in
148:43 

148:43 person.
148:45 

148:45 >> Yeah, that was in the email.
148:47 

148:47 That's in the email we sent out. That
148:49 

148:49 was clear in the email that we sent. It
148:52 

148:52 had the two different links in it. Um
148:55 

148:55 but um it's a little less clear if you
148:57 

148:57 just go to the website in order to try
149:01 

149:01 to register. I mean, if you come to the
149:03 

149:03 hub site
149:06 

149:06 um and you're here on the DDSG hub. Yep.
149:10 

149:10 >> And here's the registration for March 19
149:13 

149:13 and 20 events. If you select this link,
149:18 

149:18 you'll see the March uh 19 event which
149:22 

149:22 you can register for and you should
149:24 

149:24 register for this one whether you're
149:26 

149:26 going to be in person or onsite. That'll
149:28 

149:28 just give you
149:30 

149:30 >> link to the webinar. Um if you click Oh,
149:33 

149:33 whoops. I did that a little too quickly.
149:35 

149:35 But at the bottom here, it um gives you
149:39 

149:39 the ability to
149:42 

149:42 uh it says registration.
149:44 

149:44 uh in person. Yeah, we did share this,
149:48 

149:48 but we didn't update the site. So, I
149:51 

149:51 think we need to update this because now
149:53 

149:53 it will take you to the
149:56 

149:56 um Ashtogis website and you can register
150:01 

150:01 and if you go through the registration
150:03 

150:03 process
150:05 

150:05 at the end there is a way to
150:08 

150:08 um see that. I'm gonna get the
150:11 

150:11 registration link and just drop it in
150:13 

150:13 the chat for everybody. That goes
150:16 

150:16 directly um to that. So, I'm going to
150:20 

150:20 stop sharing for a minute just because I
150:22 

150:22 got to find that um
150:27 

150:27 um
150:42 

150:42 Um, I'm I'm trying to do that while um
150:46 

150:46 I'm talking here, so pardon me for the
150:52 

150:52 dead air. Um, but I'll get the link for
150:56 

150:56 that.
151:03 

151:03 Um,
151:11 

151:11 so there'll
151:26 

151:26 session three. Okay. Um
151:30 

151:30 well, um
151:36 

151:36 trying to find that link and I'm not
151:38 

151:38 finding it yet. Um
151:43 

151:43 >> Roger, wasn't the link that or the the
151:45 

151:45 thing that you just shared, wasn't that
151:47 

151:47 for the GIS, which is not the same as
151:50 

151:50 the DDWG?
151:52 

151:52 Yeah, that's the link to register for
151:55 

151:55 ASHTO GIST, but the um DDSG meeting is
152:00 

152:00 taking place there. Um I I know where to
152:04 

152:04 find it here. Um
152:07 

152:07 hold on. Um
152:13 

152:13 okay. Um
152:16 

152:16 now copy.
152:20 

152:20 All right. I'm putting this in the chat
152:23 

152:23 and I'll go there in a minute. Um, I
152:26 

152:26 think I got this right. Um,
152:30 

152:30 we just need to add this link to the
152:33 

152:33 bottom of the web page. Um, but we it
152:36 

152:36 was in an email that we sent to everyone
152:40 

152:40 um
152:42 

152:42 at some point. Don't know exactly when
152:44 

152:44 that went out. Wait a second. Um,
152:47 

152:47 where's the share? There we go.
152:55 

152:55 Now, this is
152:58 

152:58 um
152:60 

152:60 the um page that you would that that
153:03 

153:03 link I put in the chat gets you to. And
153:06 

153:06 then um this is the registration on
153:09 

153:09 Ashtto's website for um the in-person
153:14 

153:14 component of the DDSG
153:17 

153:17 meeting. So um
153:21 

153:21 that link is in the website or in the
153:25 

153:25 chat and this
153:27 

153:27 >> tells you about the event.
153:29 

153:29 >> Roger, you you sent the link to me
153:32 

153:32 directly, not to everyone. Could you
153:34 

153:34 post it?
153:35 

153:35 >> Sure. Um
153:37 

153:37 yeah, sorry about that. I got to change
153:40 

153:40 that to everyone.
153:43 

153:43 >> I put it in the chat just now.
153:45 

153:45 >> Oh, okay. Thanks. Thanks.
153:50 

153:50 Yeah. Um,
153:52 

153:52 that should get everybody that's here
153:54 

153:54 and we'll update the web page with that.
153:57 

153:57 Um, and it did go out in an email from
154:02 

154:02 NIBs. Uh, uh, that here. Um,
154:14 

154:14 so I think it went out like this. and
154:16 

154:16 you if you um got this email from NIBs
154:21 

154:21 um it has the two kinds of links in it,
154:26 

154:26 but the web page needs an update there.
154:29 

154:29 So, appreciate that question. and we'll
154:31 

154:31 get that taken care of um and updated on
154:35 

154:35 the web page uh so that it's clear how
154:39 

154:39 to get to the registration
154:42 

154:42 for inperson.
154:47 

154:47 Okay. Um sorry for not having that
154:50 

154:50 completely worked out but
154:52 

154:52 >> thank you.
154:53 

154:53 >> I think that does as best we can with it
154:56 

154:56 here today. Matt.
154:60 

154:60 >> Yeah. No, thanks. Thanks for the the
155:02 

155:02 highlight. Uh we'll we'll get that uh
155:06 

155:06 firmed up so that it's clear for
155:08 

155:08 everybody that goes to the website.
155:14 

155:14 Okay. Um
155:18 

155:18 All right. Well, I think we can adjourn.
155:22 

155:22 Again, I I appreciate everybody's
155:24 

155:24 involvement. Uh blessed to be part of
155:26 

155:26 the group. uh uh blessed that you uh
155:29 

155:29 chose to spend the last few hours with
155:31 

155:31 us and uh be part of the dialogue. Thank
155:34 

155:34 you so much. More to come. Um we'll keep
155:38 

155:38 getting information out on the website,
155:40 

155:40 so check back often. Thank you. Enjoy
155:43 

155:43 the rest of your afternoon.
155:45 

155:45 >> Thanks. Miss everybody.
156:06 

156:06 All right, Roger. I think I'll close out
156:07 

156:07 the webinar now.
156:09 

156:09 >> Sounds good, Rackley. Thanks for your
156:11 

156:11 help and good luck with the rest of the
156:12 

156:12 event. Hope it goes well for you and you
156:16 

156:16 uh you enjoy it.
156:18 

156:18 >> Absolutely. All right, everybody. Thank
156:20 

156:20 you.
156:21 

156:21 >> Yep. Bye.