00:25 Hello everybody. We will get started
00:27 

00:27 momentarily.
00:29 

00:29 See, we got a lot of people coming in as
00:31 

00:31 they get their reminders uh hitting
00:35 

00:35 their computers. So, just a moment.
00:37 

00:37 We'll get started.
01:37 

01:37 All right, it's a couple minutes after,
01:40 

01:40 so we'll go ahead and get started. Um,
01:44 

01:44 welcome to our digital delivery
01:46 

01:46 stakeholder group uh virtual meeting.
01:48 

01:48 This is our second set of meetings for
01:52 

01:52 the DDSG as we try to get into a regular
01:56 

01:56 cadence um and get our legs underneath
02:00 

02:00 us to move forward and understand what's
02:03 

02:03 going on in the community. Um we did
02:06 

02:06 have our inaugural meeting um last
02:09 

02:09 October
02:11 

02:11 uh and we'll touch on some of those
02:12 

02:12 items that we covered then.
02:14 

02:14 Unfortunately, it fell at uh a time in
02:18 

02:18 the calendar where there was a lot of
02:20 

02:20 the budget negotiations happening at the
02:23 

02:23 national and federal level. And so I and
02:26 

02:26 um some of the other Federal Highway
02:29 

02:29 Administration
02:30 

02:30 team involved with the project were
02:32 

02:32 unable to participate. Uh fortunately we
02:36 

02:36 had Roger and Mona uh in the NIBS team,
02:40 

02:40 the National Institute for Building
02:42 

02:42 Science on our support contract help us
02:45 

02:45 uh through that and was able to still
02:47 

02:47 execute our inaugural meeting um despite
02:51 

02:51 uh my inability to participate. But uh
02:55 

02:55 I'm happy to be here uh in front of you
02:57 

02:57 today um to discuss the DDSG and the
03:01 

03:01 efforts moving forward recognizing that
03:04 

03:04 our audience is definitely growing and
03:08 

03:08 has grown even from our inaugural
03:10 

03:10 meeting. So um we will try to touch on
03:13 

03:13 some background items uh when
03:16 

03:16 appropriate without getting into or
03:19 

03:19 repeating uh things from the previous
03:21 

03:21 meetings. some of the members um that
03:24 

03:24 have been engaged from the get-go might
03:26 

03:26 find some of it redundant, but um as we
03:30 

03:30 build momentum and and uh build out our
03:33 

03:33 audience, I want to make sure that we're
03:35 

03:35 bringing everybody up along um with us
03:38 

03:38 in the discussions.
03:40 

03:40 Um before uh introducing everybody on
03:43 

03:43 the DDSG and doing a roll call, uh I
03:47 

03:47 will have Roger forward to our standard
03:50 

03:50 disclaimer just for the record on the
03:53 

03:53 next slide. Um so you know basically
03:58 

03:58 this is saying uh that what we're
03:60 

03:60 discussing is is really the opinions of
04:02 

04:02 each individual's presenter. they don't
04:04 

04:04 represent
04:06 

04:06 uh the voice of our agency or reflect
04:09 

04:09 any kind of official policy by Federal
04:11 

04:11 Highway, the US DOT and that any uh
04:16 

04:16 discussion on manufacturers or you know
04:19 

04:19 company names, trademarks etc are just
04:22 

04:22 for the sake of open discussion and uh
04:25 

04:25 essential to the conversation when we
04:27 

04:27 talk about you know uh activities around
04:30 

04:30 the country but only forformational
04:32 

04:32 purposes and don't reflect any
04:34 

04:34 preference or endorsement of of any said
04:38 

04:38 product or company.
04:41 

04:41 >> All right,
04:41 

04:41 >> Matt. Um, maybe this is a point I don't
04:44 

04:44 know if we said that we are recording
04:46 

04:46 the meeting today so everyone is aware
04:49 

04:49 of that or maybe you were going to get
04:51 

04:51 to it, but
04:52 

04:52 >> yeah,
04:53 

04:53 >> it's kind of a disclaimer. That's a
04:55 

04:55 >> good absolutely. Yeah. Uh, hopefully you
04:59 

04:59 all got a a notice when you came into
05:01 

05:01 the meeting, but we are recording. We do
05:03 

05:03 plan to make these recordings available
05:06 

05:06 publicly um for uh you know general use.
05:11 

05:11 Um we'll touch on how we're going to do
05:13 

05:13 that and some of our mechanisms to get
05:16 

05:16 information out to everybody through uh
05:19 

05:19 websites and other correspondents um as
05:21 

05:21 we move forward. But yeah, thanks Roger
05:24 

05:24 for highlighting that. If you do not
05:27 

05:27 agree to I guess be recorded in in any
05:30 

05:30 way or fashion, then you always have the
05:31 

05:31 option to uh remove yourself or leave
05:34 

05:34 leave the meeting. Um, I hope that that
05:38 

05:38 us recording it does not uh um
05:41 

05:41 discourage uh any conversation or
05:43 

05:43 discourse because our intention is to
05:45 

05:45 have open dialogue and and be able to to
05:47 

05:47 to speak openly about what's going on
05:50 

05:50 around the country with regards to uh
05:52 

05:52 digital delivery and and progress and
05:55 

05:55 understand where challenges and and
05:57 

05:57 things are are happening and kind of the
05:59 

05:59 state of the community.
06:03 

06:03 Um, next slide, Roger. Yeah. Um, so I'm
06:06 

06:06 uh Matt Corgan. I'm a Federal Highway
06:08 

06:08 Administration. Um, I'm in our uh office
06:12 

06:12 of infrastructure analysis and
06:13 

06:13 construction team rather the team within
06:16 

06:16 the office of research and development
06:19 

06:19 here at uh Turner Fairbank Highway
06:21 

06:21 Research Center um which is located in
06:24 

06:24 Northern Virginia just outside of the
06:25 

06:25 Washington DC area. Um again we have the
06:30 

06:30 National Institute for uh building
06:32 

06:32 science is helping us with our support
06:35 

06:35 contract to um manage the efforts in the
06:38 

06:38 group. So, we've got uh Roger and
06:42 

06:42 Rackley and Mona uh participating as
06:44 

06:44 well and they'll be helping with
06:46 

06:46 logistics and through some of our uh
06:48 

06:48 interactions and use of Menty and Mural
06:52 

06:52 and and some of the other mechanisms
06:54 

06:54 that we're looking to have that dialogue
06:55 

06:55 and feedback and and make sure that we
06:58 

06:58 give everybody an opportunity to have a
06:60 

06:60 voice. Um if uh you are you know
07:04 

07:04 listening and you do want to uh provide
07:08 

07:08 uh any questions or comments or or
07:10 

07:10 perspectives um we definitely want to
07:13 

07:13 encourage that. And so, uh, you know,
07:15 

07:15 you can raise your hand, um, within the
07:17 

07:17 the Zoom, uh, platform and queue up and
07:21 

07:21 and we'll, uh, make sure through the
07:23 

07:23 help of the NIB staff that, um, we get
07:26 

07:26 that interaction and and give you the
07:28 

07:28 ability to come into the conversation as
07:30 

07:30 well.
07:33 

07:33 >> And, um, alternatively, Matt, people can
07:35 

07:35 put things in the chat and we will see
07:38 

07:38 them there as well. And that can be in
07:42 

07:42 addition to speaking. It's not one or
07:44 

07:44 the other. So, the chat's another way to
07:47 

07:47 reach out during the meeting. And we'll
07:48 

07:48 be talking about a couple of other um
07:52 

07:52 tools we're going to use for for
07:53 

07:53 engagement and interaction in a in a
07:55 

07:55 bit.
07:57 

07:57 >> Yeah, absolutely. Yeah. Again, we we
07:60 

07:60 these meetings are are open um and we're
08:03 

08:03 we're really, you know, anxious to make
08:05 

08:05 sure that we have uh open dialogue and
08:09 

08:09 uh give everybody the opportunity to
08:10 

08:10 participate um however you choose
08:13 

08:13 whether it's through the chat or raising
08:16 

08:16 your hand or through mural and menty and
08:18 

08:18 the other mechanisms that we'll get to.
08:21 

08:21 Thanks, Roger, for the reminder.
08:26 

08:26 And um so we do have what we would
08:28 

08:28 consider a core membership uh of the
08:31 

08:31 digital delivery stakeholder group. The
08:33 

08:33 members are indicated here. Um it
08:35 

08:35 represents a diversity of state agencies
08:39 

08:39 as well as industry uh perspectives
08:42 

08:42 through some of the association
08:45 

08:45 um that are listed. Uh we wanted to make
08:48 

08:48 sure that we had uh not only a broad
08:51 

08:51 range of maturity
08:53 

08:53 um in their digital delivery journey, if
08:56 

08:56 you will, uh from those that are very
08:58 

08:58 much uh advancing and you know uh at the
09:02 

09:02 forefront of of these initiatives as
09:04 

09:04 well as those that are just starting
09:06 

09:06 their journey. Um there's uh some
09:09 

09:09 obvious I think regional distribution
09:11 

09:11 that you'll see here as well as well as
09:14 

09:14 ensuring that we've got some
09:16 

09:16 cross-pollination and representation on
09:18 

09:18 the various ASHTO technical uh
09:20 

09:20 committees um that are working in this
09:23 

09:23 space uh and and again the the industry
09:26 

09:26 partnerships. Now you know some of the
09:28 

09:28 the associations we did ask for them to
09:31 

09:31 uh determine who is going to represent
09:33 

09:33 them as an entity. Um and so um those
09:37 

09:37 those uh individuals are really speaking
09:40 

09:40 on behalf of their association and
09:42 

09:42 larger community and and helping us to
09:45 

09:45 engage with them and understand you know
09:47 

09:47 those industry perspectives as well
09:49 

09:49 which is very important here. Um I'm
09:52 

09:52 going to use this list just to go down
09:54 

09:54 uh these these members here are also
09:56 

09:56 represented as panelists. So, those of
09:59 

09:59 you who got the panelist invitations,
10:01 

10:01 you have the ability to come in and
10:03 

10:03 unmute yourself or uh share your video
10:05 

10:05 as you feel comfortable. But I'm just
10:07 

10:07 going to use this opportunity and this
10:09 

10:09 list to go down and do a roll call for
10:12 

10:12 us to just to take record of of who's
10:14 

10:14 online. Um, so as I go down through the
10:17 

10:17 list and mention your name, feel free
10:19 

10:19 just to uh you know unmute yourself and
10:22 

10:22 um say hello and uh you know uh
10:25 

10:25 introduce yourself to the group and the
10:27 

10:27 audience at large. Um,
10:29 

10:29 >> hey Matt, one one other thing might be
10:31 

10:31 if for some reason we didn't get you as
10:33 

10:33 a panelist and you're out there, please
10:36 

10:36 raise your hand and we'll we'll promote
10:38 

10:38 you up to panelist and and uh connect
10:41 

10:41 with you if if one of the members maybe
10:44 

10:44 we missed out on that somehow.
10:46 

10:46 >> Yeah. Excellent. Good good uh
10:50 

10:50 good notice.
10:54 

10:54 Um
10:56 

10:56 so uh I'll just stop start at the top.
10:59 

10:59 Uh this isn't the only order that this
11:02 

11:02 is is basically alphabetical. So don't
11:04 

11:04 don't worry about any kind of
11:06 

11:06 organizational
11:08 

11:08 uh listing here or you know first uh is
11:12 

11:12 not the most important although Cassidy
11:13 

11:13 is very important to the conversation.
11:15 

11:15 But uh um Cassidy are you on?
11:19 

11:19 >> I am and you're stealing all my jokes.
11:24 

11:24 No, I'm Cassidy Blauers. I'm a Delas
11:27 

11:27 construction resource engineer, which
11:28 

11:28 means I'm in charge of a lot of our
11:30 

11:30 digital delivery efforts and
11:31 

11:31 coordinating them with other sections of
11:33 

11:33 the department. I'm also on uh
11:36 

11:36 construction. I'm chair of the uh
11:38 

11:38 innovative construction technology
11:40 

11:40 committee and also on Jason.
11:43 

11:43 >> Thanks, Cassidy. Rick Price.
11:50 

11:50 I
11:50 

11:50 >> think Rick said he was gonna miss one of
11:53 

11:53 these meetings.
11:56 

11:56 I know Katie's on. Katie,
11:58 

11:58 >> yes, I am here. Uh, my name is Katie
12:01 

12:01 Brown. I am the state digital delivery
12:04 

12:04 engineer for Oklahoma DOT.
12:09 

12:09 And uh Cindy
12:13 

12:13 Cindy might have said she was gonna have
12:15 

12:15 somebody else represent her.
12:17 

12:17 >> Uh good morning and good afternoon
12:20 

12:20 everybody. I'm Brian McKinnus. Uh Cindy
12:22 

12:22 actually asked that I could st if I
12:24 

12:24 could stand in for her today um and
12:27 

12:27 represent on behalf of uh ARPA and our
12:30 

12:30 board membership there.
12:32 

12:32 >> Excellent. Welcome.
12:34 

12:34 >> Thank you. Will Holmes.
12:40 

12:40 Where's Will? Don't see Will on the
12:43 

12:43 panelist.
12:46 

12:46 Ian,
12:48 

12:48 it's Ian online.
12:52 

12:52 No, Ian. Uh,
12:56 

12:56 Carrie.
13:01 

13:01 Think we got regrets from Carrie. Uh
13:05 

13:05 yeah. Yeah.
13:07 

13:07 >> Okay. And Jennifer
13:14 

13:14 Jennifer. Oh, Kevin.
13:24 

13:24 Allan. Is he Allan?
13:26 

13:26 >> I am here. Uh Alan Melly. I am the chief
13:30 

13:30 of the digital delivery section at the
13:33 

13:33 Pennsylvania Department of
13:34 

13:34 Transportation.
13:38 

13:38 >> Devin,
13:39 

13:39 >> good morning. Devon Poor. I am the uh
13:42 

13:42 Calrans BIM Fry program director and um
13:45 

13:45 the lead for our digital delivery and
13:48 

13:48 BIM efforts uh within the department.
13:52 

13:52 >> Deon and Jonathan.
13:56 

13:56 >> Good afternoon everybody. Jonathan
13:58 

13:58 Porter with AGC of America. I'm the
13:60 

14:00 highway and transportation division
14:02 

14:02 director.
14:04 

14:04 >> Thanks, Jonathan. And Charlie.
14:08 

14:08 >> Hello everybody. I'm Charlie Purcell. I
14:10 

14:10 serve as the deputy director of our
14:11 

14:11 transportation development division here
14:13 

14:13 at Iowa DOT and I also serve as our
14:16 

14:16 executive champion for our digital
14:18 

14:18 delivery efforts.
14:21 

14:21 Sure.
14:23 

14:23 And Dan
14:29 

14:29 can see Dan.
14:31 

14:31 Trisha.
14:34 

14:34 Hi everybody. Trisha Stfansky, Minnesota
14:37 

14:37 Department of Transportation. I direct
14:39 

14:39 our asset management office. I'm also
14:41 

14:41 chair of Jstan. Um I'll talk about that
14:44 

14:44 a little bit later, so stick with us. As
14:47 

14:47 well as I'm co-chair of building smart
14:49 

14:49 roads and bridges um USA.
14:53 

14:53 Welcome, Trisha, Jacob.
14:56 

14:56 >> Good morning, everyone. Jacob Tambonga,
14:58 

14:58 director of digital delivery for Texas
14:60 

14:60 Department of Transportation. Um, glad
15:02 

15:02 to meet all of y'all.
15:04 

15:04 >> And
15:06 

15:06 Brad,
15:11 

15:11 >> Brad, no. Okay. Um, yeah. So that that's
15:16 

15:16 the official membership, but again, you
15:17 

15:17 know, we want to make sure that that
15:19 

15:19 we're engaging, you know, holistically.
15:22 

15:22 Um we we did plan this meeting as all
15:26 

15:26 virtual. Uh we'll talk about some
15:28 

15:28 planning in future meetings. Our uh goal
15:31 

15:31 is to have in-person hybrid meetings um
15:35 

15:35 as well as virtual meetings in between
15:38 

15:38 those um on a regular cadence. Um so
15:42 

15:42 this being our second meeting is is just
15:45 

15:45 a virtual presentation. Um but we will
15:48 

15:48 have an opportunity to to kind of uh get
15:51 

15:51 on site at some other venues um for us
15:54 

15:54 to concentrate. So, we broke the meeting
15:56 

15:56 up uh as a virtual meeting into three
15:59 

15:59 sessions over three days to hopefully
16:02 

16:02 facilitate participation and recognizing
16:05 

16:05 that you know there's um it's hard to
16:07 

16:07 get everybody especially when you're
16:09 

16:09 virtual to dedicate entire day or a
16:12 

16:12 couple days uh online. So, um but we can
16:15 

16:15 you know discuss that moving forward um
16:18 

16:18 as far as what's uh most useful for the
16:20 

16:20 membership to to continue our meetings.
16:23 

16:23 Uh the purpose for for this meeting is
16:25 

16:25 is just to continue efforts as the you
16:28 

16:28 know a collaborative initiative
16:31 

16:31 um where we want to integrate you know
16:33 

16:33 all these different areas of digital
16:35 

16:35 delivery uh across the country and uh
16:38 

16:38 understand where everybody's at and
16:41 

16:41 where the activities are and where there
16:44 

16:44 are opportunities for uh you know
16:47 

16:47 addressing uh either gaps or uh things
16:50 

16:50 that could be strengthened um etc. So,
16:54 

16:54 uh, and again just reemphasizing that
16:56 

16:56 it's an open, you know, open group and
16:59 

16:59 open meeting. So, we're not, uh, you
17:01 

17:01 know, meeting behind closed doors and,
17:04 

17:04 um, it it's really meant to to to really
17:07 

17:07 engage everybody in the community. But,
17:15 

17:15 and for our agenda today, um, we do have
17:20 

17:20 the broken up over the next three days.
17:22 

17:22 uh session one. Um uh you know today was
17:26 

17:26 really primarily targeted at us uh kind
17:29 

17:29 of going over uh what we did at the last
17:32 

17:32 meeting which was really kind of just to
17:33 

17:33 set the stage and get everybody at a
17:35 

17:35 base level with a lot of efforts and
17:38 

17:38 activities um uh that you will hear some
17:42 

17:42 updates um today as well. the ASHTTO
17:45 

17:45 efforts through their committees as
17:47 

17:47 Trisha had mentioned and Jennifer uh
17:50 

17:50 involved uh specifically we'll likely
17:53 

17:53 have uh a regular occurrence during our
17:56 

17:56 meetings to give us update and also have
17:59 

17:59 uh an understanding from them how this
18:01 

18:01 group can help them with their efforts
18:04 

18:04 and how um you know they can leverage us
18:08 

18:08 to participate in any of their efforts
18:10 

18:10 moving forward or or any of their
18:12 

18:12 products and and things that are being
18:14 

18:14 uh developed and delivered as well. Um
18:17 

18:17 the rest of the uh meeting agenda over
18:20 

18:20 the next uh two days with session two
18:23 

18:23 and session three um our intent was to
18:27 

18:27 have an item where we're addressing uh
18:30 

18:30 two very major significant uh pulled
18:33 

18:33 transportation pulled fund or TPF
18:36 

18:36 efforts uh that are being done at a
18:38 

18:38 national level that involve a lot of uh
18:41 

18:41 state DOS and have contributed funding
18:44 

18:44 uh in order to advance both BIM
18:47 

18:47 uh for bridges and structures or the BIM
18:49 

18:49 FB nomenclature
18:51 

18:51 as well as the uh BIM for infrastructure
18:55 

18:55 or BIM FI uh TPF's transportation bold
18:59 

18:59 funds. We were going to do that one day
19:01 

19:01 and then pivot and give some
19:03 

19:03 opportunities to discuss some of our
19:05 

19:05 ADCMS uh grant efforts uh that are uh
19:09 

19:09 being done by a lot of the states that
19:11 

19:11 tie into a lot of the digital delivery
19:13 

19:13 efforts as well. uh from a timing
19:16 

19:16 perspective, we did have to mix them up.
19:18 

19:18 Um so we have a little bit of both those
19:20 

19:20 areas on the next two days uh in order
19:23 

19:23 to accommodate uh people's schedules.
19:25 

19:25 And so we're uh happy that everybody was
19:28 

19:28 able to to make some adjustments and and
19:31 

19:31 help us to figure out the appropriate
19:33 

19:33 scheduling. Um but that's what we have
19:35 

19:35 on the agenda the next few days uh in
19:38 

19:38 case you're trying to strategize, you
19:40 

19:40 know, your involvement or or where you
19:42 

19:42 want to participate. Um hopefully we can
19:45 

19:45 uh get your uh attention throughout all
19:48 

19:48 three of those and contribute, but uh we
19:50 

19:50 understand that everybody's uh facing a
19:53 

19:53 lot of um activities and uh time
19:56 

19:56 constraints and so you may not be able
19:58 

19:58 to.
20:01 

20:01 Um Roger, you want to touch on the other
20:05 

20:05 engagement efforts that we have set up?
20:08 

20:08 Yeah, we um we're going to use uh
20:10 

20:10 Mentometer and Mural during our meeting
20:12 

20:12 today to um also hear from you all out
20:16 

20:16 there and engaged with you. Uh so the
20:19 

20:19 first thing we wanted to do is introduce
20:21 

20:21 the mentometer and um get everyone into
20:26 

20:26 it and let you give us a little bit of
20:28 

20:28 information about you all that are out
20:31 

20:31 there in the audience so we can know
20:34 

20:34 about your background. So, um if you can
20:38 

20:38 put in you can either scan this QR with
20:41 

20:41 your phone.
20:43 

20:43 Um we can uh uh drop that URL into the
20:49 

20:49 chat. Whoops. I don't know if I can do
20:52 

20:52 it from my um Rackley, can you drop that
20:56 

20:56 URL in the chat for the menty? Are you
20:59 

20:59 able to get that?
21:02 

21:02 Um, I don't think it'll let me do it
21:04 

21:04 while I'm in presentation mode to copy
21:07 

21:07 it.
21:08 

21:08 >> It's in the chat, Roger.
21:10 

21:10 >> Okay. So, you can either use the QR,
21:13 

21:13 click on the uh the link in the chat or
21:16 

21:16 go to Menty and put in the access code,
21:19 

21:19 and that should get you to the first
21:21 

21:21 question. Um,
21:24 

21:24 maybe uh let's see, Mona, is there
21:27 

21:27 anything else you want to say about
21:28 

21:28 that? I guess it would be good if I got
21:31 

21:31 that on the screen though, right? So we
21:33 

21:33 can
21:34 

21:34 >> Yeah, I share my screen here if you'd
21:37 

21:37 like.
21:38 

21:38 >> So,
21:39 

21:39 >> okay, why don't you do that? Yeah.
21:40 

21:40 >> All right. So, I've sent the request and
21:42 

21:42 it just so everybody knows if you go to
21:45 

21:45 menty.com, you can dial in 88621750.
21:50 

21:50 It looks like a lot of you are in there.
21:52 

21:52 We've got 61 folks from the state DOS,
21:54 

21:54 12 federal highway, 10 consultants. Can
21:58 

21:58 you show? I'm not seeing your screen,
21:59 

21:59 Mona. If you think you're sharing.
22:01 

22:01 >> All right. I've submitted the request to
22:03 

22:03 share.
22:04 

22:04 >> Well, you have I relinquished. So, if
22:06 

22:06 you go to share in the bottom. Yeah.
22:08 

22:08 >> Can you see it? There we are.
22:10 

22:10 >> Now, we can.
22:11 

22:11 >> All right. Outstanding. So, I see all of
22:13 

22:13 the results coming in again.
22:15 

22:15 Code8621750@y.com.
22:20 

22:20 And we'll have a few more survey
22:22 

22:22 questions here in a little bit, but for
22:24 

22:24 now it'll give us a good understanding
22:25 

22:25 of who's participating and you know the
22:28 

22:28 basic representation of all of the folks
22:30 

22:30 here. It's great to see more than 200
22:33 

22:33 people on the call today. So that's
22:34 

22:34 fantastic. So if you can get in that
22:36 

22:36 would be awesome. You could use it on um
22:39 

22:39 your computer or your phone. You can
22:40 

22:40 scan the QR code or go on your phone to
22:43 

22:43 menty.com code 88621750.
22:49 

22:49 >> All right. Thanks. We'll keep that
22:51 

22:51 >> keep this question open.
22:53 

22:53 >> Roger and uh Rackley, I'm getting some
22:57 

22:57 uh correspondence outside of uh this
23:01 

23:01 meeting that says that the chat is
23:03 

23:03 disabled for the participants.
23:09 

23:09 Oh.
23:09 

23:09 >> Oh, that shouldn't be.
23:12 

23:12 >> Um,
23:20 

23:20 >> so perhaps we can figure
23:23 

23:23 >> we can work on that as we're going along
23:26 

23:26 here. Um, okay. I will um that's good
23:31 

23:31 distribution and it also helps us look
23:33 

23:33 at the areas where we want to keep
23:35 

23:35 building involvement. So, um, this is
23:39 

23:39 very helpful. Uh, let's go. I'll go back
23:42 

23:42 to the slides.
23:44 

23:44 >> I've, uh, I've enabled it. Um,
23:48 

23:48 I thought I had preset that, but I guess
23:49 

23:49 not. But it seems to be resolved now.
23:55 

23:55 >> Great.
23:56 

23:56 >> Yeah, looks like we got some. Perfect.
23:60 

23:60 Um, I see somebody's got their hand
24:02 

24:02 raised. Is that Brandt? Uh, Vermeier.
24:05 

24:05 I'm not sure if that's intentional at
24:08 

24:08 this point or accidental.
24:12 

24:12 And
24:14 

24:14 nope.
24:16 

24:16 Uh,
24:18 

24:18 Jacob,
24:21 

24:21 there's lots of hands.
24:34 

24:34 All right. Um, are we set with that? We
24:37 

24:37 can now talk about the other engagement
24:40 

24:40 tool we um want to use and that's Mural.
24:43 

24:43 And we're going to do a little overview
24:45 

24:45 of Mural and uh show you what we've set
24:48 

24:48 up, get you in there, show you what
24:50 

24:50 we've set up and and and uh encourage
24:54 

24:54 you to engage with it and use it. Um,
24:59 

24:59 Brackley, do you want me to show it and
25:01 

25:01 you um
25:04 

25:04 uh
25:06 

25:06 uh we can I can follow you or do you
25:09 

25:09 want to take
25:10 

25:10 >> I can take it over.
25:12 

25:12 >> Okay.
25:13 

25:13 Um then you can I'll stop sharing and
25:17 

25:17 you can share.
25:24 

25:24 >> Alrighty.
25:26 

25:26 Is this coming through? Okay.
25:28 

25:28 I'm seeing it. Yes.
25:31 

25:31 >> Okay, let me quickly drop the um
25:38 

25:38 link into the
25:43 

25:43 bar link
25:48 

25:48 into the chat really quick just so that
25:51 

25:51 everybody can join it more easily.
26:00 

26:00 There we are.
26:09 

26:09 Uh, did that go? Let's see. Yeah, that
26:12 

26:12 chat went to everyone, right?
26:14 

26:14 >> I believe so.
26:16 

26:16 >> Okay.
26:19 

26:19 Uh now a few people are saying nope cuz
26:23 

26:23 it said it went to panelists to me. So
26:25 

26:25 maybe it's where um I can try and get it
26:28 

26:28 in there if that while you're while
26:30 

26:30 you're getting started correctly.
26:32 

26:32 >> Oh well it said it went to hosts and
26:34 

26:34 panelists. Oh hosts and panelists not
26:36 

26:36 everyone. Fantastic.
26:48 

26:48 >> Okay. It should be
26:49 

26:49 >> everyone's in.
26:51 

26:51 >> Fantastic.
26:55 

26:55 >> Let's celebrate with some confetti. That
26:57 

26:57 seems fun.
27:02 

27:02 All right. So, we'll just give it
27:04 

27:04 a wait for me to see how many people are
27:06 

27:06 in at the
27:14 

27:14 72.
27:18 

27:18 Yeah,
27:18 

27:18 >> we'll we'll give it a minute.
27:20 

27:20 >> Right. So, uh first order of business,
27:23 

27:23 um this is a collaborative space. So,
27:25 

27:25 the very first thing we want to do
27:26 

27:26 because there are so many people in here
27:28 

27:28 is we kindly ask that you uh turn off
27:32 

27:32 your mouse tracers because it's really
27:33 

27:33 hard to see where all the pointers are,
27:35 

27:35 you know, zooming around everywhere. To
27:36 

27:36 do that, you go down to the bottom here,
27:38 

27:38 you zoom over your icon, which will be
27:40 

27:40 the farthest left one, and you deselect
27:42 

27:42 broadcast my cursor.
27:46 

27:46 So, if everybody could do that, um, just
27:48 

27:48 so that there's not two million uh
27:50 

27:50 little little cursors zooming all over
27:52 

27:52 the place, that would be excellent.
27:57 

27:57 Yeah. And there's lots of interesting
27:58 

27:58 ways to react. I mean, there's a
27:59 

27:59 reaction button, you know, you can do
28:02 

28:02 confetti and all kinds of all kinds of
28:04 

28:04 stuff. Um, just as we go through this,
28:08 

28:08 there's lots of ways to to use the draw
28:10 

28:10 tool. Uh but mainly what we're going to
28:13 

28:13 be working with are our sticky notes.
28:15 

28:15 Right. Exactly. Um
28:19 

28:19 so there uh
28:22 

28:22 as as we go through this, you know, we
28:24 

28:24 have different uh
28:27 

28:27 uh different items on here. We have the
28:29 

28:29 agenda for the uh three different
28:31 

28:31 meetings. If we look over here, today's
28:33 

28:33 meeting is marked in in green here. In
28:36 

28:36 fact, I can request to I can ask you to
28:39 

28:39 be followed. So you can all follow what
28:41 

28:41 I'm looking at as you're as you're
28:42 

28:42 looking at this. So if you would all
28:44 

28:44 accept that, that would be probably more
28:45 

28:45 convenient than trying to watch both
28:47 

28:47 things at the same time.
28:59 

28:59 >> And yeah, if you put a if you put a
29:01 

29:01 postit where you don't want it, you can
29:03 

29:03 just um highlight it and right shift and
29:06 

29:06 delete it.
29:07 

29:07 >> Yeah.
29:12 

29:12 Right. So the idea behind this is to
29:14 

29:14 have a a continuous workspace um where
29:20 

29:20 we can do collaboration. Uh so for
29:23 

29:23 example this right here uh you know just
29:25 

29:25 general meeting comments like if
29:26 

29:26 something's working you like something
29:29 

29:29 ideas for uh next meetings ideas for the
29:31 

29:31 mural uh unanswered questions feel free
29:34 

29:34 to drop those in here. Uh you can sign
29:36 

29:36 it with your name uh if it's something
29:38 

29:38 you would want to be attributed to you.
29:41 

29:41 If you want to stay anonymous, that's
29:42 

29:42 also okay. You're um when you sign into
29:45 

29:45 this, you automatically are anonymized
29:48 

29:48 unless you specify a name. Uh you'll be
29:50 

29:50 given an animal name um of some sort.
29:54 

29:54 Um yes, if you if you do make uh if you
29:57 

29:57 double click it makes a sticky note. If
29:59 

29:59 you leave it somewhere you don't want
30:00 

30:00 it, it's very easy to delete it. You
30:02 

30:02 just click on it again and hit delete.
30:04 

30:04 Um, so yeah, if there's comments you
30:05 

30:05 want to leave, feel free to use this.
30:07 

30:07 And as I move down here, you'll see that
30:09 

30:09 we have on different slides we're about
30:10 

30:10 to see. Uh, comments, questions,
30:13 

30:13 concerns, you can leave sticky notes in
30:14 

30:14 this green box here. Uh, you can resize
30:17 

30:17 your sticky note, you can change the
30:18 

30:18 color of it, the font size, you can add
30:20 

30:20 icons to it on the left here. Um,
30:22 

30:22 there's all kinds of things you can do.
30:24 

30:24 Uh, it's pretty fun. Uh, so we have
30:26 

30:26 stuff for bin modeling. Uh we'll have
30:29 

30:29 things for the the website. We'll be
30:30 

30:30 talking about the Chicago meeting. Uh
30:33 

30:33 other dates. Um if there's calendar
30:35 

30:35 dates that are not on this calendar that
30:37 

30:37 you want to make known, you can add them
30:38 

30:38 here. Uh we'll be talking about previous
30:40 

30:40 survey results. Uh we'll get back to the
30:42 

30:42 menty meter later. Uh yes, hello to you
30:46 

30:46 as well. Um and then talking about JSAN
30:49 

30:49 and JTCE.
30:51 

30:51 Um so this is what we're going to be
30:53 

30:53 doing for the three different meetings.
30:54 

30:54 Right now we just have today's um and I
30:58 

30:58 just want to make make sure that we
31:00 

31:00 realize that this will carry over
31:02 

31:02 between meetings and uh we're hoping
31:04 

31:04 that this mural can become a place where
31:07 

31:07 uh we can collaborate and even smaller
31:09 

31:09 groups on different issues. Uh this is
31:12 

31:12 permanent. That link you just got
31:13 

31:13 consider saving it uh because you can
31:16 

31:16 always come back to this. It will always
31:17 

31:17 be here. Uh, and as we build this out,
31:20 

31:20 you know, we'll have sections all over
31:21 

31:21 the place where you can feel free to,
31:23 

31:23 you know, collaborate with other people
31:24 

31:24 and leave leave notes and and it's
31:26 

31:26 really great. There's lots of incredible
31:28 

31:28 templates available um in here to to
31:31 

31:31 help that. You don't have to build all
31:33 

31:33 these things yourself.
31:35 

31:35 Um, and I think that's everything for
31:37 

31:37 the mural. Feel free to use this as the
31:39 

31:39 meeting is going on to leave comments
31:40 

31:40 and feedback. Of course, we also have
31:41 

31:41 the chat and raising your hand. I
31:43 

31:43 apologize that I've been uh talking for
31:45 

31:45 so long, but uh I think that's
31:47 

31:47 everything with Mural. Roger, do you
31:49 

31:49 have any other notes? Matt,
31:53 

31:53 >> no. This is helpful. Um I I think some
31:57 

31:57 people probably aren't as familiar with
31:59 

31:59 Mural. So, uh thanks for that kind of uh
32:02 

32:02 brief primer. Just a reminder again as
32:05 

32:05 people come in because it it can get
32:07 

32:07 very busy with all the cursors. If you
32:10 

32:10 go down in the bottom and identify your
32:12 

32:12 cursor, you can toggle off broadcast
32:15 

32:15 your cursor and that'll make it a little
32:17 

32:17 less cluster uh cluttered if you will.
32:20 

32:20 Um and then you know like when Rackley's
32:23 

32:23 in there or if we're in there on a
32:24 

32:24 specific area if you want to follow them
32:26 

32:26 um you can select somebody and you can
32:28 

32:28 follow them that way. You know you can
32:30 

32:30 follow along as they're scrolling and
32:32 

32:32 moving versus you trying to keep up as
32:35 

32:35 well. Um so that makes it a little bit
32:37 

32:37 easier. Um but as we go through uh the
32:40 

32:40 rest of the presentations and you'll see
32:42 

32:42 those slides represented in an area if
32:45 

32:45 you want to provide comments or sticky
32:47 

32:47 notes um in those areas as well as our
32:50 

32:50 other engagement uh activities it would
32:52 

32:52 be great. Um
32:55 

32:55 and uh let's see we're getting some
32:58 

32:58 webinar chat somebody said about an
33:00 

33:00 echo. I'm not having any audio issues on
33:03 

33:03 my end. So that may be the users uh
33:06 

33:06 issue with regards to Echo. Um that
33:09 

33:09 doesn't seem to be an issue for me uh
33:12 

33:12 hearing any of the nib staff are
33:14 

33:14 following along.
33:16 

33:16 Um
33:17 

33:17 >> same here.
33:20 

33:20 >> And uh Julie's asking about how to
33:22 

33:22 follow again. So that's in mural. I
33:25 

33:25 think if you go down to the bottom of
33:27 

33:27 your mural, um, you probably hopefully
33:29 

33:29 you've got multiple screens going
33:31 

33:31 because it's probably difficult to have,
33:33 

33:33 yeah, if you're just on a laptop screen
33:35 

33:35 or a single screen to be able to use
33:37 

33:37 these. But if you've got multiple
33:39 

33:39 screens and you leave mural and um the
33:43 

33:43 menty up throughout, it'll be easier for
33:47 

33:47 you to access. But in Mural, if you go
33:49 

33:49 down to the bottom where the icons are,
33:51 

33:51 um, if you want to follow somebody,
33:53 

33:53 Rackley is there. um like I was
33:55 

33:55 following him, but you can basically uh
33:58 

33:58 click on Rackley RW um and select follow
34:03 

34:03 Rackly Ren um or you could follow
34:06 

34:06 anybody else for that matter, I guess.
34:08 

34:08 And then you'll just follow along as
34:10 

34:10 they navigate through the site.
34:15 

34:15 >> And uh I like the uh crowdsource too.
34:18 

34:18 There are certainly people out there
34:19 

34:19 that use Mural. You can help others in
34:22 

34:22 with questions in the chat. We
34:24 

34:24 appreciate that. So, um, all right.
34:27 

34:27 Shall we move on? We'll come back to
34:29 

34:29 Muro. We know it takes a little while
34:31 

34:31 people to get checked out on it
34:33 

34:33 sometimes, but don't be afraid. You
34:35 

34:35 can't break anything. And the idea is
34:37 

34:37 try to give your input to things as we
34:39 

34:39 go through, Matt said. So,
34:42 

34:42 >> great.
34:42 

34:42 >> Yeah. And and I think I think primarily
34:44 

34:44 too, you know, the sticky notes are
34:46 

34:46 probably the most effective way to do
34:48 

34:48 that. And so on that left toolbar there
34:51 

34:51 is the sticky note uh icon that you can
34:55 

34:55 click on and you can select you know
34:57 

34:57 size or color. So for example where you
35:00 

35:00 know Rackley's at um in the the four
35:04 

35:04 quadrants there's colors for uh each of
35:07 

35:07 those quadrants if you want to match up
35:09 

35:09 with those colors to make it a little
35:10 

35:10 easier to sort those. Um if not and
35:13 

35:13 they're just in that quadrant I think we
35:15 

35:15 can figure it out. But the sticky note
35:18 

35:18 icon uh on the left bar will allow you
35:20 

35:20 to make those changes as well.
35:24 

35:24 Um and you know certainly if you want to
35:26 

35:26 be anonymous you can you can do that but
35:28 

35:28 we would encourage you to identify
35:30 

35:30 yourself. It just helps us to be able to
35:32 

35:32 understand positions and you know the
35:35 

35:35 perspectives and and other things as we
35:38 

35:38 uh continue to track our activities and
35:40 

35:40 you know where areas of importance or
35:42 

35:42 emerging areas are or uh maybe less um
35:47 

35:47 less urgent areas so we can help
35:49 

35:49 prioritize those things as well.
35:58 

35:58 Okay. Is my screen coming through?
36:01 

36:01 >> It is, Roger. Yes.
36:02 

36:02 >> Yeah. Okay.
36:05 

36:05 >> Um, so to to kind of recap um you know,
36:09 

36:09 kind of where we're at uh uh today. Um
36:12 

36:12 and and I know the members this is going
36:14 

36:14 to be a little bit of redundancy, but to
36:18 

36:18 get everybody caught up again, um you
36:20 

36:20 know, our first meeting was uh very
36:23 

36:23 concise. at a short window of time. We
36:25 

36:25 were at the I Heatap meeting um to
36:27 

36:27 leverage a lot of the attendance that uh
36:30 

36:30 that generates especially with our
36:32 

36:32 members in digital delivery. Um but it
36:35 

36:35 really just was was given an opportunity
36:37 

36:37 for us to set the stage with the ASHTO
36:40 

36:40 committees with some of the programmatic
36:42 

36:42 areas. um have the associations provide
36:46 

36:46 their perspectives and uh most of the
36:49 

36:49 associations that that have membership
36:52 

36:52 have policy statements, you know,
36:54 

36:54 endorsing and supporting digital
36:56 

36:56 delivery uh if you're involved through
36:58 

36:58 uh those associations.
37:01 

37:01 You may already be aware of those, but
37:02 

37:02 they can certainly point you to those um
37:05 

37:05 policy statements or endorsements as as
37:08 

37:08 needed. I would encourage you to reach
37:10 

37:10 out to to your association member uh if
37:13 

37:13 you need to do that. Um but uh you know
37:16 

37:16 as far as you know why we're here uh on
37:19 

37:19 the next slide Roger um
37:23 

37:23 these are kind of the core elements and
37:26 

37:26 we we do have a a charter um that's been
37:29 

37:29 established that kind of lays out you
37:30 

37:30 know these kind of things purpose
37:32 

37:32 objectives kind of the scope who we are
37:35 

37:35 as well as who we are not um and some of
37:38 

37:38 the logistics as far as membership that
37:40 

37:40 I mentioned and you know meetings um the
37:43 

37:43 link uh is at the bottom. We'll have to
37:46 

37:46 duplicate that, Roger, in the chat if we
37:49 

37:49 can so people can access the the
37:51 

37:51 charter. Um but that will give you all
37:53 

37:53 the details that you see concisely put
37:56 

37:56 up here in in bullet form. Um probably
38:00 

38:00 uh not necessarily more important than
38:02 

38:02 who we are. Um but certainly uh needing
38:06 

38:06 to recognize uh who we are or what we're
38:09 

38:09 not interested in um discussing is is
38:13 

38:13 you know for example we're not here to
38:16 

38:16 to discuss you know things that would be
38:18 

38:18 considered you know uh market
38:19 

38:19 competition and pricing and things that
38:22 

38:22 you know competitive space um we uh we
38:26 

38:26 are not established under the federal
38:29 

38:29 advisory committee uh um meaning the
38:33 

38:33 federal advisory committee act which is
38:35 

38:35 in a United States code has a very form
38:39 

38:39 for formal uh requirements if the DDSG
38:44 

38:44 was formed in order to uh solicit
38:47 

38:47 guidance to federal highway or the US
38:50 

38:50 DOT
38:52 

38:52 uh andor any of the administrations and
38:54 

38:54 and modes and so we are not established
38:57 

38:57 under that so we are not soliciting uh
39:00 

39:00 nor are we going to you know entertain
39:02 

39:02 if somebody is going to try to provide
39:05 

39:05 any kind of advice to us as an agency.
39:07 

39:07 That's not something that uh we are
39:09 

39:09 going to do during this meeting. So, I
39:11 

39:11 think it's important to highlight that
39:13 

39:13 there's a lot of great things that we
39:15 

39:15 anticipate being and being able to do,
39:17 

39:17 but that is one of the areas that we
39:20 

39:20 have to be cog uh cognizant of um with
39:23 

39:23 regards to the federal advisory
39:24 

39:24 committee act. So, I do want to
39:26 

39:26 highlight that. That's also highlighted
39:28 

39:28 in the charter. Um all the charter uh
39:31 

39:31 all the members are listed on the
39:33 

39:33 charter as well. So if you've got a need
39:36 

39:36 to to reach out or follow up on who the
39:38 

39:38 membership is, you'll see that. Um and
39:40 

39:40 there is a an ethics statement that uh
39:43 

39:43 pretty much everybody's agreed to as
39:45 

39:45 participation and you know reaffirming
39:48 

39:48 you know that ethics statement uh to
39:50 

39:50 make sure that we're all uh endeavoring
39:52 

39:52 to be you know uh open and productive
39:55 

39:55 and and honest enterprise.
39:59 

39:59 Roger, is there anything here you feel
40:01 

40:01 like we need to go into more detail
40:05 

40:05 at this stage? No, maybe just to
40:07 

40:07 highlight, you know, that I mean Federal
40:10 

40:10 Highways established this group as a way
40:14 

40:14 for to collaborate together and to try
40:17 

40:17 to leverage all the things that are
40:19 

40:19 going on and reduce uh any duplications
40:24 

40:24 and share information and highlight the
40:27 

40:27 critical activities. And you know, it's
40:29 

40:29 meant to be a group for the for us in
40:32 

40:32 the industry to leverage and use. we're
40:35 

40:35 trying to like facilitate it, bring it
40:38 

40:38 together, but it's really your group in
40:40 

40:40 a way or everyone that's here to take
40:43 

40:43 advantage of and use and so we hope you
40:46 

40:46 all kind of, you know, participated in
40:48 

40:48 it with that spirit in mind. That takes
40:50 

40:50 a little while to maybe get in place,
40:53 

40:53 but that's the goal. So, I think keeping
40:55 

40:55 that in mind is really helpful and
40:58 

40:58 important.
40:59 

40:59 >> Yeah. Thanks, Roger. And some of you may
41:02 

41:02 be asking I guess like what what is
41:04 

41:04 digital delivery and we we did you know
41:07 

41:07 try to address that within the charter
41:09 

41:09 as well um within the the first page of
41:12 

41:12 the document. It certainly is very
41:14 

41:14 broad. There are a lot of uh efforts and
41:16 

41:16 activities um you know under this
41:19 

41:19 umbrella of digital delivery uh and
41:22 

41:22 they're all in various stages of
41:23 

41:23 maturity and use. And so we recognize
41:25 

41:25 that you know this is a a big endeavor
41:28 

41:28 and you know this this meeting is is
41:30 

41:30 really your meeting as well um to to
41:33 

41:33 have that conversation and dialogue. Uh
41:35 

41:35 we don't want to just dictate you know
41:37 

41:37 to the audience uh what we're doing uh
41:40 

41:40 but we also want to hear what's going on
41:43 

41:43 uh you know from your perspective and
41:45 

41:45 your part of uh industry and and agency
41:48 

41:48 and business use and business need case
41:51 

41:51 um within digital delivery. But it is is
41:54 

41:54 definitely a broad area uh because it
41:57 

41:57 covers so many aspects of you know an
41:60 

41:60 asset from you know planning all the way
42:02 

42:02 through uh asset management,
42:04 

42:04 maintenance, decommissioning and the
42:06 

42:06 next project as well.
42:13 

42:13 um you know to to restate kind of the
42:15 

42:15 the vision if you will. Um you know this
42:18 

42:18 this comes underneath
42:21 

42:21 um what we published uh uh not too long
42:25 

42:25 ago uh the advancing BIM for
42:28 

42:28 infrastructure national strategic
42:30 

42:30 roadmap. Um you can access that uh at
42:33 

42:33 the Rosa P uh repository.
42:36 

42:36 um that address there. Uh uh I know you
42:39 

42:39 can't click on it again. Roger. Could we
42:42 

42:42 maybe get get that link posted in the
42:45 

42:45 chat as well?
42:47 

42:47 >> Yeah, Rackley, you can do that. I can't
42:49 

42:49 copy paste
42:51 

42:51 while I'm in present mode, but
42:54 

42:54 >> yeah, no worries.
42:56 

42:56 >> The the BIM uh for infrastructure
42:59 

42:59 national strategic roadmap um you know,
43:02 

43:02 this is where this graphic comes out of
43:04 

43:04 it. It kind of sets, you know, kind of
43:06 

43:06 that baseline and vision um that we're
43:08 

43:08 all working towards. Uh we are uh
43:12 

43:12 planning to revisit uh this document and
43:15 

43:15 dive into it a little more detail to see
43:17 

43:17 how we've progressed. There are kind of
43:19 

43:19 maturity measures if you will. And so we
43:21 

43:21 want to understand uh kind of the level
43:24 

43:24 of maturity or how we've progressed even
43:26 

43:26 in the short time since uh this document
43:29 

43:29 was published. but also as we move
43:30 

43:30 forward uh there are uh some agencies
43:34 

43:34 and parts of industry that are uh very
43:37 

43:37 much further ahead than other parts. Um
43:40 

43:40 but we will be revisiting this road map
43:42 

43:42 because it does really kind of set the
43:43 

43:43 baseline if you will of the expectations
43:46 

43:46 and where we're looking to to move uh
43:49 

43:49 moving forward. And it's often also
43:52 

43:52 referenced when it comes to other
43:54 

43:54 activities uh that we have in place at
43:56 

43:56 the national level whether it's through
43:58 

43:58 you know uh funding and grant uh
44:00 

44:00 mechanisms through the ADCMS
44:03 

44:03 uh grant program or uh other efforts and
44:06 

44:06 we expect that there's going to be other
44:08 

44:08 opportunities for us to revisit and
44:10 

44:10 maybe uh update um this uh roadmap
44:14 

44:14 moving forward. is not necessarily I
44:17 

44:17 think envisioned to be static in a you
44:19 

44:19 know one time and be done um since we
44:21 

44:21 will definitely be learning uh more uh
44:25 

44:25 you know uh as we move forward about
44:27 

44:27 where people's activities are and where
44:29 

44:29 their level maturity is and we may even
44:31 

44:31 identify areas that we need to
44:33 

44:33 strengthen or provide more detail.
44:38 

44:38 Um and we are planning at our our next
44:41 

44:41 meeting to go a little bit deeper dive
44:42 

44:42 into the uh this road map item uh more
44:45 

44:45 specifically.
44:51 

44:51 If you have not had the opportunity to
44:53 

44:53 digest that, I encourage you to do that.
44:55 

44:55 Um again, it's a lot of good
44:57 

44:57 information. Um in fact, I I need to go
45:01 

45:01 back and and reread it myself. It's been
45:03 

45:03 a little bit a while since I read
45:05 

45:05 through it in detailed it when we were,
45:07 

45:07 you know, working to to develop the DDSG
45:09 

45:09 and get it off the ground and um uh I
45:12 

45:12 always glean more nuggets of of insight
45:15 

45:15 or other details as I uh continue to
45:18 

45:18 digest it in more detail.
45:20 

45:20 >> And uh it could be helpful. NIBs had a
45:23 

45:23 webinar a couple of months ago now that
45:26 

45:26 Terry Klene from Infoch and I presented
45:29 

45:29 on the road map. So you can find that in
45:32 

45:32 NIB's um site archives of events might
45:36 

45:36 be a way to get a refresher on it. Um we
45:39 

45:39 can put that link make that link
45:42 

45:42 available to people too um when we get a
45:44 

45:44 chance.
45:49 

45:49 >> Thanks Roger.
45:55 

45:55 And um so some of the things that you
45:59 

45:59 know that has happened in the short
46:01 

46:01 amount of time is you know certainly we
46:03 

46:03 initiated the DDSG and solicited the
46:06 

46:06 membership and got agreement you know to
46:08 

46:08 try and you know get up get up off the
46:10 

46:10 ground. Um and and we had our inaugural
46:13 

46:13 meeting uh at I HEAP. Um we do have uh
46:17 

46:17 resources available for everybody to
46:20 

46:20 access uh that information. uh and we we
46:24 

46:24 intend to continue to update it with
46:26 

46:26 recordings and presentations moving
46:28 

46:28 forward. Um you can find that
46:32 

46:32 information at our uh digital delivery
46:34 

46:34 stakeholder hub. Uh that address is
46:38 

46:38 there on the screen uh as well in the
46:40 

46:40 the webinar chat. Um and if if uh if you
46:45 

46:45 are just searching you know online if
46:48 

46:48 you put D digital delivery stakeholder
46:50 

46:50 group or DDSG
46:52 

46:52 um you may not get to the page. I've
46:54 

46:54 found that in my experience if I add hub
46:57 

46:57 and I specifically include hub in the
46:60 

46:60 search query. Usually uh it pops right
47:02 

47:02 up. So, um just a a little nugget of uh
47:06 

47:06 uh insight if you're just using a a
47:09 

47:09 search functionality uh within a browser
47:12 

47:12 is to include the hub and it should pop
47:14 

47:14 up uh then for you to bookmark or
47:16 

47:16 whatever. Uh of course planning our you
47:18 

47:18 know the meeting today uh that we have
47:21 

47:21 split across the three days the 22nd,
47:23 

47:23 26th and 28th. Um and then we have a
47:27 

47:27 third meeting that is going to be our
47:29 

47:29 our hybrid joint in person and virtual.
47:32 

47:32 Again, our meetings are intended to be
47:34 

47:34 open. We will have a virtual component
47:36 

47:36 uh for everyone. Uh but we also have
47:38 

47:38 resources through our support contract
47:41 

47:41 for the DOT members for us to be on site
47:44 

47:44 together um in order to continue to
47:47 

47:47 foster that collaboration and and
47:49 

47:49 dialogue and um recognizing that it's
47:52 

47:52 often easier for us to concentrate um
47:55 

47:55 you know when we can get uh uh away from
47:58 

47:58 our uh regular office duties and all the
48:01 

48:01 things that pull us in multiple
48:02 

48:02 directions and make it difficult to
48:04 

48:04 sometimes uh be fully engaged in a
48:07 

48:07 virtual only setting um in that uh
48:10 

48:10 on-site and hybrid. We are collloic
48:13 

48:13 colllocating with the ASHTO GIST
48:16 

48:16 conference. Um that's a has been an
48:19 

48:19 annual item of the the GIS uh portion of
48:25 

48:25 uh transportation community. Um we are
48:28 

48:28 uh leveraging that as an opportunity for
48:30 

48:30 us to engage uh with them for those of
48:33 

48:33 us on site that might be able to have
48:36 

48:36 additional resources from uh our own
48:39 

48:39 agencies to participate in the GIS
48:41 

48:41 conference. you know plan to uh that is
48:44 

48:44 you know the preceding week leading up
48:46 

48:46 to this meeting and then at the end uh
48:49 

48:49 leveraging you know those that are on
48:51 

48:51 site engaging GIS uh to be able to
48:54 

48:54 participate with us on that Thursday
48:56 

48:56 afternoon the 19th and uh the Monday of
49:00 

49:00 the um Friday the 20th. Um those
49:05 

49:05 registration items are posted on the hub
49:09 

49:09 uh location as well. So if you go to uh
49:12 

49:12 the hub and you find our upcoming
49:16 

49:16 meetings, you'll see the registration
49:18 

49:18 details for this hybrid one. Um just be
49:22 

49:22 aware that there are two registration
49:24 

49:24 mechanisms. One if you're going to be
49:26 

49:26 participating virtual and the other if
49:29 

49:29 you're planning to be on site. And
49:31 

49:31 there's registration and um uh hotel
49:35 

49:35 room information uh through the Ashtto
49:39 

49:39 room block. uh if you plan to be on site
49:42 

49:42 and make those arrangements. So those
49:43 

49:43 are two separate um registration
49:46 

49:46 mechanisms that are posted on the hub
49:50 

49:50 and we will continue to plan for
49:52 

49:52 additional meetings. Um I certainly
49:54 

49:54 appreciate the grace that's been
49:56 

49:56 extended uh uh to us by the DDSG
49:59 

49:59 membership. uh our goal is to make sure
50:02 

50:02 that we're you know getting information
50:04 

50:04 out uh both to the members and the
50:06 

50:06 broader community much earlier uh than
50:08 

50:08 what uh we've been able to do for these
50:11 

50:11 first couple of meetings um as we get
50:14 

50:14 into that regular cadence. So, I
50:16 

50:16 appreciate that, Grace. But we will be
50:18 

50:18 trying to get, you know, planning and
50:20 

50:20 get dates locked down and locations and
50:22 

50:22 and uh we'll discuss that in more detail
50:25 

50:25 uh towards the end of today as we wrap
50:28 

50:28 up and and re-engage the the actual
50:30 

50:30 members on a few of those items to make
50:32 

50:32 sure we're moving in a direction that
50:34 

50:34 allows the majority of us to be able to
50:36 

50:36 participate uh as much as possible.
50:42 

50:42 And thanks again to Roger and uh staff
50:44 

50:44 for uh helping prop up our hub.
50:48 

50:48 >> Yeah, maybe I'll just give a quick view
50:51 

50:51 of the hub, Matt. Um to show people a
50:54 

50:54 couple things quickly. Um I think we can
50:56 

50:56 we'll drop the URL in the chat. Note
50:59 

50:59 that we also have this in the mural. If
51:01 

51:01 you're still in the mural and you want
51:03 

51:03 to leave us any comments on the hub, we
51:06 

51:06 welcome that. um and would be happy to
51:10 

51:10 um um respond to those. Um so, uh let me
51:15 

51:15 see. Here's the homepage of the hub that
51:19 

51:19 you'll find. A couple quick things um
51:22 

51:22 across the top here. This is inside
51:25 

51:25 NIB's site. So, these things are NIB's
51:27 

51:27 wrapper, but these things are all about
51:30 

51:30 the DDSG
51:31 

51:31 hub. And let's say you want to see the
51:34 

51:34 objectives of the DDSG. If you come down
51:37 

51:37 here, um, you can find them. But one
51:40 

51:40 little thing we haven't solved yet is
51:43 

51:43 that when you're in this section and you
51:46 

51:46 use these tabs, it will give you
51:48 

51:48 information. Um, and those same tabs are
51:51 

51:51 the ones that are up here, but um, it
51:54 

51:54 takes a doubleclick. Um, that wasn't a
51:57 

51:57 good example. I want to show you where
51:59 

51:59 the resources are. So if I come down
52:02 

52:02 here, it's it's still on community. I
52:06 

52:06 have to click resources again. We're
52:08 

52:08 trying to find a solution to that. But
52:11 

52:11 um we mentioned before the charter the
52:14 

52:14 charter is available here. Also all the
52:17 

52:17 presentations from our um first event
52:21 

52:21 are here and the uh recording is I I
52:25 

52:25 guess it isn't posted yet. We were still
52:28 

52:28 we had some trouble with splitting it up
52:30 

52:30 to process it, but we will get that on
52:33 

52:33 there um any time now. And then the
52:37 

52:37 events are listed here so that you can
52:39 

52:39 register for those as Matt was talking
52:41 

52:41 about. And finally, you can uh get
52:44 

52:44 involved and leave your name on here for
52:47 

52:47 us and that way we can make sure we
52:50 

52:50 communicate with you about when meetings
52:52 

52:52 are coming, any new things the group is
52:54 

52:54 doing, etc. And we'll be adding more
52:57 

52:57 things to this site um as we go forward.
53:02 

53:02 Um so um that's the DDSG
53:06 

53:06 um site. Um and um
53:12 

53:12 yeah, if you um want to look at it and
53:15 

53:15 leave us any comments, we appreciate
53:17 

53:17 them. Um
53:19 

53:19 so um I think that's quick good overview
53:23 

53:23 of what's there. Um
53:29 

53:29 and so now I guess we were we wanted to
53:32 

53:32 just flag you've already kind of talked
53:34 

53:34 about it right Matt our our upcoming
53:37 

53:37 meeting and we wanted to come back to
53:39 

53:39 that at the end of the day and and do a
53:42 

53:42 little bit of discussion about the
53:44 

53:44 agenda which is just a very high level
53:47 

53:47 preliminary thing so far.
53:52 

53:52 >> Yeah. Yeah. And and again just you know
53:54 

53:54 there we expect that there's going to be
53:56 

53:56 some standing items because of the
53:58 

53:58 importance and the amount of activities
53:60 

53:60 such as the you know the transportation
54:02 

54:02 flip fund studies and items. We're going
54:05 

54:05 to hear uh from them uh throughout the
54:07 

54:07 the next couple of meetings that we have
54:09 

54:09 scheduled here uh to discuss their
54:12 

54:12 activities and you know uh how we can
54:14 

54:14 engage with them and how we can provide
54:17 

54:17 um any resources or you know review or
54:20 

54:20 perspectives uh as a community that they
54:22 

54:22 might need. um and and you know other
54:26 

54:26 activities as well that you know with
54:28 

54:28 the how broad the topic is there's a lot
54:31 

54:31 of uh activities going on and we want to
54:34 

54:34 hear from the community. So you know if
54:36 

54:36 there are other research efforts whether
54:38 

54:38 it's through a national cooperative
54:40 

54:40 highway research program that dovetales
54:42 

54:42 into this area or a state you know le
54:45 

54:45 research with a uh one of their academic
54:48 

54:48 institutions
54:50 

54:50 um or other industry you know uh efforts
54:52 

54:52 and items to highlight. Uh we certainly
54:55 

54:55 want to to hear about those and and have
54:57 

54:57 an opportunity you know to provide any
54:59 

54:59 comments or feedback on those items as
55:02 

55:02 well. Devin I see your hand up. you want
55:04 

55:04 to go go ahead and come on.
55:07 

55:07 >> Well, yeah. I was just gonna say, uh,
55:09 

55:09 Roger, I don't know if they fixed it
55:10 

55:10 since the last time because when I
55:13 

55:13 scrolled down, I clicked on the
55:14 

55:14 resources tab, it showed up right away,
55:15 

55:15 but it it seems as though you just have
55:18 

55:18 two separate banners on the same page
55:20 

55:20 and the top banner where you click
55:23 

55:23 resources, it just moves you to the
55:24 

55:24 bottom of the page and then regardless,
55:27 

55:27 you have
55:28 

55:28 >> you have to.
55:29 

55:29 >> That's why.
55:31 

55:31 >> Yeah. Sorry, Devon. That's what I tried
55:33 

55:33 to point out. We're trying to fix that,
55:34 

55:34 but we haven't found a quick solution
55:37 

55:37 for it yet. So that when you click up
55:39 

55:39 here, it will coordinate with resources
55:43 

55:43 down here. The way it's currently set up
55:46 

55:46 is when you click up here on, let's say
55:48 

55:48 we want to see the objectives, but it's
55:50 

55:50 still showing the resources. It
55:53 

55:53 highlighted this box, but you have to
55:54 

55:54 click on it. So I know that's a little
55:57 

55:57 inconvenient and we're trying to fix it,
55:58 

55:58 but um I had point I did want to
56:01 

56:01 >> point that out.
56:03 

56:03 Okay. No, that makes sense. I uh I don't
56:05 

56:05 know why, but like when I had just
56:06 

56:06 clicked on, I was like, "Wait a minute.
56:07 

56:07 It's just working." But then I
56:09 

56:09 >> there's two separate banners, so that's
56:11 

56:11 the pro. Okay. Thanks.
56:12 

56:12 >> They will line up eventually, but for
56:14 

56:14 some reason, whatever the the utility
56:18 

56:18 is, it's not a straightforward thing.
56:20 

56:20 So,
56:23 

56:23 okay. Um and I had briefly shown there
56:26 

56:26 the um the the um mural and if you you
56:31 

56:31 can find those two areas in the mural
56:34 

56:34 you can if you want to leave any
56:36 

56:36 comments there um like that about the
56:40 

56:40 website we will be w we'll welcome those
56:43 

56:43 things and we're going to talk more
56:44 

56:44 about the agenda as Matt said. Um, all
56:47 

56:47 right. Well, let let me see. Let get
56:49 

56:49 back to the U presentation then. Um,
56:57 

56:57 and the next thing up was going to be um
57:02 

57:02 the schedule of events which we were
57:04 

57:04 also planning to talk about later, right
57:07 

57:07 Matt? So, we can come back to this.
57:10 

57:10 >> Yeah. I think the the thing I'll mention
57:12 

57:12 here is um again you know like like we
57:15 

57:15 want to make sure we understand you know
57:19 

57:19 major significant items that you know
57:23 

57:23 are happening or occurring through the
57:25 

57:25 year. uh to be able to make sure that,
57:28 

57:28 you know, either we identify an
57:30 

57:30 appropriate event that perhaps we can
57:33 

57:33 work with um to have one of our on-site
57:36 

57:36 meetings um or to avoid um so that we
57:40 

57:40 don't have conflicts to make sure that
57:42 

57:42 uh you know again we're able to to
57:44 

57:44 engage the community and have everybody
57:46 

57:46 participate. So, um, we will circle back
57:49 

57:49 to this as Roger said towards the end of
57:51 

57:51 the meeting today when we talk about
57:53 

57:53 upcoming schedule and, uh, time frames.
57:56 

57:56 Um, but if you might, you know, be
57:59 

57:59 thinking about, you know, what you have
58:00 

58:00 on your calendars or checking your
58:02 

58:02 calendar for any significant conflicts
58:04 

58:04 or items. Um, we're trying to find, uh,
58:07 

58:07 the best mechanism to help us kind of
58:10 

58:10 crowdsource that information or populate
58:12 

58:12 it. Um as you see here in this slide, we
58:15 

58:15 do have a few items, you know,
58:17 

58:17 identified coming up, particularly on
58:19 

58:19 some of the major ashtto meetings, you
58:22 

58:22 know, like the um committee on design or
58:24 

58:24 committee on construction, uh those kind
58:27 

58:27 of things, but there are others that
58:29 

58:29 that we know are surely out there. Um
58:32 

58:32 and and likewise, if you go into the
58:34 

58:34 mural, um and you see this particular
58:38 

58:38 slide that shows the the schedule, um
58:41 

58:41 there's the ability to uh add a post-it
58:45 

58:45 notes. So if you have any events um that
58:48 

58:48 are locked in with dates and times and
58:50 

58:50 locations, you can populate uh that in
58:54 

58:54 detail there and help us kind of
58:56 

58:56 crowdsource that information uh as much
58:58 

58:58 as possible to to help us with future
59:01 

59:01 planning.
59:07 

59:07 >> Great. Um
59:15 

59:15 So, next up is going to be yeah, summary
59:19 

59:19 of findings from meeting one, but let me
59:21 

59:21 uh let's just make uh
59:24 

59:24 time check here. It's one um okay. Yeah,
59:29 

59:29 we're in
59:31 

59:31 we're um in good shape. So, um
59:37 

59:37 we'll move into talk about this now.
59:42 

59:42 >> Yeah. Yeah. You know, I think just to to
59:45 

59:45 reaffirm, Roger, before you kind of go
59:47 

59:47 over kind of, you know, what what
59:49 

59:49 resulted out of the first meeting is,
59:51 

59:51 you know, again, we want to make sure
59:53 

59:53 that we're understanding where the
59:55 

59:55 community is and having that engagement.
59:57 

59:57 And so, you know, that's why we're we're
59:59 

59:59 bringing, you know, these tools to help
60:01 

60:01 leverage those. If if you've got any,
60:03 

60:03 you know, recommendations, if you have
60:05 

60:05 access or know of other tools, um, that
60:08 

60:08 could be useful in this space,
60:10 

60:10 certainly, you know, reach out to us. if
60:12 

60:12 you've um you know something comes to
60:15 

60:15 mind after the meeting or next week that
60:18 

60:18 you know you're like oh I wish I would
60:19 

60:19 have brought that up or this would have
60:21 

60:21 been a good item to to mention you again
60:23 

60:23 you can go back into that mural and you
60:25 

60:25 can you can provide those comments or
60:27 

60:27 provide that information um uh you know
60:30 

60:30 Roger and I you know our our information
60:34 

60:34 is easily accessible uh through the hub
60:37 

60:37 and and other mechanisms feel free to
60:39 

60:39 reach out to us um you know we we I I
60:42 

60:42 will say for myself, I won't always get
60:44 

60:44 back to you immediately, but as I as I
60:47 

60:47 go through my my queue, I I definitely
60:49 

60:49 will get back to you and respond to you.
60:51 

60:51 Uh it just may not be, you know, right
60:53 

60:53 away that day. Um uh because of uh all
60:56 

60:56 the other things that that we have uh in
60:59 

60:59 the pipeline, but um
61:03 

61:03 yeah. So, Roger, if you want to kind of
61:06 

61:06 >> Yeah. Okay. Um engage.
61:09 

61:09 >> Thanks, ma'am. Uh yeah. So th the we
61:12 

61:12 wanted to so in this section this is
61:15 

61:15 kind of where we want to engage with you
61:17 

61:17 all. But first we're just going to give
61:19 

61:19 a little overview of what happened at
61:22 

61:22 the first meeting um and what we learned
61:25 

61:25 from both the discussions there and the
61:29 

61:29 uh use of mentometer the polling that we
61:32 

61:32 did. So, I'm going to review those
61:35 

61:35 things first and then um we're going to
61:38 

61:38 open the menntter back up and um give
61:42 

61:42 you a chance to engage with us in the in
61:46 

61:46 the mentometer. Uh and also the mural is
61:49 

61:49 out there if and these findings and the
61:52 

61:52 uh meeting one survey results are there.
61:55 

61:55 So, if you were there and you have any
61:57 

61:57 comments you want to make or additions
61:59 

61:59 you want to make or if you weren't and
62:01 

62:01 you have questions or something you
62:02 

62:02 don't, you know, understand, um, put
62:05 

62:05 them out there on the mural, drop them
62:07 

62:07 into the chat. Um, uh, uh, try to, you
62:11 

62:11 know, um, get any questions, thoughts
62:15 

62:15 you have shared or into the proceedings
62:18 

62:18 here so we can take advantage of those
62:21 

62:21 and what we're doing going forward. So
62:24 

62:24 after we um did the meeting one, these
62:27 

62:27 were kind of the highlevel findings that
62:30 

62:30 we um uh identified as being critical um
62:38 

62:38 for the meeting or the critical outcomes
62:41 

62:41 from the meeting. And um I think this
62:44 

62:44 first one is no no surprise. um you know
62:48 

62:48 having a workforce that's ready and
62:51 

62:51 dealing with everything it takes to get
62:53 

62:53 that in place is a significant challenge
62:57 

62:57 um to scaling up and you know there's
63:01 

63:01 the challenge of doing pilots which is
63:04 

63:04 kind of where we are now and then
63:06 

63:06 scaling beyond that and so I think this
63:10 

63:10 is a really interesting challenge um and
63:14 

63:14 I'm sure that's one of the advantages of
63:17 

63:17 or one of the ideas of connecting with
63:19 

63:19 these ADCMS projects. We can learn about
63:22 

63:22 the piloting and be thinking about this
63:25 

63:25 uh the the Oklahoma project that we're
63:27 

63:27 going to hear from on Monday. Um uh
63:31 

63:31 Katie, if I've got this right, this is
63:33 

63:33 an objective of that uh ADCMS and how
63:37 

63:37 what we do to get there. That's part of
63:39 

63:39 what they're taking on looking at. So
63:41 

63:41 we'll be considering that on Monday and
63:44 

63:44 then moving more into that discussion on
63:47 

63:47 uh at our next meeting. We'll talk about
63:49 

63:49 that on Monday. Um you know there's a
63:52 

63:52 lot of activity on standards alignment
63:55 

63:55 and interoperability.
63:57 

63:57 I would note that this includes I think
63:60 

63:60 really both the standards work but also
64:03 

64:03 the technology work, the software tools
64:07 

64:07 that we have. And I think most of us
64:10 

64:10 would agree the software is out there.
64:12 

64:12 It has the capabilities to do BIM and
64:16 

64:16 support digital delivery, but it isn't
64:19 

64:19 set up to utilize the workflows and the
64:22 

64:22 standards and the processes that we want
64:25 

64:25 to try and share and leverage to advance
64:28 

64:28 industry forward. It's kind of different
64:31 

64:31 silos that are trying to be broken down.
64:34 

64:34 So, I think this includes both of those
64:36 

64:36 things and it's an important concept.
64:40 

64:40 Um, you know, we need leadership. Many
64:43 

64:43 of us have talked about this. We've got
64:44 

64:44 to get not just those of us who are um
64:48 

64:48 in there doing things, but also the
64:50 

64:50 whole organization, the executive
64:53 

64:53 leadership to understand and participate
64:56 

64:56 and be committed. Uh, and we've tried to
64:59 

64:59 consider that in this group and work on
65:02 

65:02 how we can engage people. But that's
65:04 

65:04 something to keep thinking about. peer
65:07 

65:07 learning um is still continues to be
65:10 

65:10 important. Hence, you know, the ADCMS
65:13 

65:13 grants sharing on those um and sharing
65:17 

65:17 on what the poolled funds are doing.
65:19 

65:19 Pool funds are have a lot of focus on
65:21 

65:21 standards and interoperability. So,
65:23 

65:23 that's kind of why we've we're really
65:25 

65:25 engaged with them and we all want to do
65:28 

65:28 this across the whole life cycle. I
65:31 

65:31 think that's critical to success. Um and
65:36 

65:36 that's something that is takes a
65:38 

65:38 continued focus to make happen. And you
65:41 

65:41 know we kind of found um progress is
65:44 

65:44 accelerating. Uh and we are in the uh we
65:48 

65:48 do have organizations in in either early
65:50 

65:50 or pilot stages. Some of those are
65:53 

65:53 starting to move a little further but um
65:56 

65:56 there's still a lot of need to continue
65:58 

65:58 to coordinate, train and share. Um, so
66:03 

66:03 this is what we found. Um, and if you,
66:07 

66:07 you know, this is in in the mural as we
66:10 

66:10 said. If you go over there and if you
66:12 

66:12 want to add any comments to those
66:15 

66:15 things, um,
66:18 

66:18 you can do that um,
66:24 

66:24 in here. Um, and we'd welcome that and
66:28 

66:28 we'll talk about it too. We can also I
66:30 

66:30 mean this is where we want to start
66:32 

66:32 getting some dialogue going on these
66:35 

66:35 things. We thought that it might be
66:36 

66:36 helpful though um I'll just take a quick
66:39 

66:39 look at the at these um the the survey
66:44 

66:44 results that led to those summary
66:46 

66:46 findings from our last meeting, but
66:48 

66:48 they're really I think pretty consistent
66:50 

66:50 with those with the summary findings. uh
66:54 

66:54 um just to you know um
66:58 

66:58 where people are um kind of reflects
67:01 

67:01 what that last statement said about
67:03 

67:03 pilots and starting to think about
67:06 

67:06 scaling. Um what are the firstear goals
67:10 

67:10 for digital delivery? Um let this bigger
67:13 

67:13 might help. Um
67:17 

67:17 um well this is first year goals for the
67:20 

67:20 stakeholder group but I think these
67:22 

67:22 priorities are more in alignment with
67:24 

67:24 the kind of summary findings standards
67:26 

67:26 and technology development training and
67:29 

67:29 credentiing
67:31 

67:31 this you know these two didn't quite
67:33 

67:33 make that final list policy advocacy and
67:38 

67:38 legal matters but I think we agree those
67:40 

67:40 are are really important um areas uh and
67:46 

67:46 the the priorities and the barriers sort
67:48 

67:48 of line up with each other. People still
67:51 

67:51 feel strongly we need good standards. Um
67:55 

67:55 we have to address change and training.
67:59 

67:59 Uh and so these things kind of all
68:01 

68:01 conspire together. uh technology
68:04 

68:04 um needs to continue to advance to align
68:08 

68:08 with the standards and the processes
68:11 

68:11 and focusing on data stewardship and
68:14 

68:14 governance and getting leadership. So I
68:18 

68:18 think there's the results that we saw
68:21 

68:21 from the first meeting are kind of
68:24 

68:24 consistent with those summary findings.
68:27 

68:27 Um,
68:28 

68:28 so now, um, Mona, I don't know if
68:31 

68:31 there's anything else you want to say
68:33 

68:33 about the meeting one surveys and kind
68:36 

68:36 of our conclusions that came out of it
68:39 

68:39 or we want to uh, open up the mentter
68:43 

68:43 now and use it to um, kind of take pulse
68:49 

68:49 on where this is and what might have
68:52 

68:52 advanced since then. uh to continue to
68:55 

68:55 give give us uh some uh uh residents
69:01 

69:01 from the community to work with.
69:03 

69:03 >> Yeah, thanks Roger. So, you know, I
69:06 

69:06 think that you gave a pretty good
69:07 

69:07 overview of how our participants
69:09 

69:09 responded at IHEA and I think we have a
69:12 

69:12 larger stakeholder group here today. So
69:14 

69:14 our effort before I jump back over to
69:16 

69:16 the um mentee survey is to really
69:19 

69:19 understand instead of just giving a
69:21 

69:21 onetoone copy of every survey question,
69:24 

69:24 we wanted to really um progress our I
69:26 

69:26 guess learning around a few different
69:28 

69:28 parts. One would be what's changed. So
69:30 

69:30 really doing a pulse check with you all
69:32 

69:32 today um that somewhat reflects the
69:34 

69:34 original questions but allows us to call
69:36 

69:36 out movement or stagnation or
69:38 

69:38 acceleration since last fall. Um, and
69:41 

69:41 some of the questions you'll see will
69:43 

69:43 really help us reframe progress in terms
69:45 

69:45 of velocity, not necessarily maturity,
69:47 

69:47 which, you know, I think is often more
69:49 

69:49 honest as well. And, uh, we ask a few
69:52 

69:52 other questions that are not necessarily
69:54 

69:54 reasking what matters, but we're asking
69:56 

69:56 what's intensified um, and helping us
69:59 

69:59 really create a before and after
69:60 

70:00 narrative without rerunning the entire
70:02 

70:02 survey. So, um, with that then I will
70:05 

70:05 switch over and share. We uh Mona before
70:08 

70:08 we do we have any questions in the chat
70:12 

70:12 or do we have anyone who wants to say
70:14 

70:14 anything about the uh first meeting that
70:18 

70:18 was there maybe um
70:22 

70:22 and we can also come back to that after
70:24 

70:24 we run through after we do the new
70:27 

70:27 surveying.
70:38 

70:38 Doesn't look like anybody's laying in
70:39 

70:39 yet. Or do we see anything coming in?
70:48 

70:48 >> Well, you can ponder that while we um
70:52 

70:52 give you some some questions to interact
70:56 

70:56 with.
70:56 

70:56 >> Absolutely. So I I believe my screen is
70:59 

70:59 being shared right now and so
71:01 

71:01 >> No, we're not seeing I'm not seeing your
71:03 

71:03 screen. Um
71:07 

71:07 >> I see I saw it.
71:09 

71:09 >> Oh, okay. So let's take a peek. I'll
71:11 

71:11 reset it. So can you see my screen?
71:14 

71:14 >> Yes.
71:15 

71:15 >> Yes.
71:16 

71:16 >> All right. Excellent. So it looks like
71:18 

71:18 we've got 174 people inside of menty.
71:21 

71:21 And if you're not in Menty, you can go
71:22 

71:22 to menty.com using code 88621750
71:26 

71:26 or use the link in the chat that Matt
71:28 

71:28 and others have dropped in. Um, all
71:31 

71:31 right, let's move on to the next
71:32 

71:32 question. So, this is going to feel
71:35 

71:35 somewhat familiar. Again, we're trying
71:36 

71:36 to really show what has changed for you
71:39 

71:39 this year compared to your efforts last
71:41 

71:41 year so that we can start to analyze any
71:44 

71:44 changes or, you know, progress that
71:45 

71:45 you've made. So this question is really
71:47 

71:47 around which DDSG focus area feels most
71:50 

71:50 critical right now and the platform will
71:52 

71:52 allow you to select up to two. So we'll
71:55 

71:55 pause here as the results come in. I'm
71:57 

71:57 starting to see them come in
71:60 

71:60 >> and let's make sure everybody has the
72:02 

72:02 link. If you don't let's make sure they
72:04 

72:04 know where to get it. They came in late.
72:07 

72:07 >> Yep. So you can go to bent.com
72:10 

72:10 nti.com
72:12 

72:12 >> and
72:12 

72:12 >> or we can put the link right in, can't
72:14 

72:14 we?
72:15 

72:15 >> And right from that page, you can also
72:16 

72:16 do 88621750
72:19 

72:19 is the code or there's the link in the
72:21 

72:21 chat that I believe has been dropped in
72:22 

72:22 there a couple times.
72:27 

72:27 All right.
72:29 

72:29 And if it's easier to do on your phone,
72:31 

72:31 you're welcome to do this on your phone
72:32 

72:32 as well. Um or on your computer. both uh
72:36 

72:36 work just fine.
72:38 

72:38 All right. So, we're going to close that
72:39 

72:39 section. It's interesting. So, most
72:41 

72:41 >> Wait, no. Give it a minute. Did you get
72:43 

72:43 what kind of do you have enough results?
72:45 

72:45 Okay.
72:46 

72:46 >> Yep. Yeah. So, it looks like most of you
72:49 

72:49 are saying that coordinating standards,
72:50 

72:50 adoption, and alignment is um
72:54 

72:54 most critical right now, which seems
72:56 

72:56 pretty consistent with change management
72:58 

72:58 being, you know, the priority, the
73:01 

73:01 largest challenge or need uh based on
73:03 

73:03 the last survey. So second would be
73:05 

73:05 supporting pilot projects and case
73:07 

73:07 studies looks like. Third is workforce
73:10 

73:10 training and credentiing. A lot of this
73:12 

73:12 falls in the change management category.
73:13 

73:13 It's less technical and more
73:15 

73:15 organizational which um I can understand
73:19 

73:19 change management is always the largest
73:21 

73:21 challenge when implementing this. The
73:23 

73:23 technical piece can be complex but the
73:25 

73:25 people and process piece is just uh as
73:28 

73:28 important if not most important. All
73:30 

73:30 right. We've got technology development
73:32 

73:32 and deployment support there. You know,
73:35 

73:35 the lease two is interesting. Updating
73:36 

73:36 the national digital delivery roadmap
73:39 

73:39 seems to be the least um critical right
73:41 

73:41 now. Legal and policy seems to be the
73:43 

73:43 least critical right now. So um
73:46 

73:46 >> it it might also be we did restrict it
73:48 

73:48 to two. So that's a little
73:52 

73:52 >> Yep.
73:54 

73:54 Yeah. Our hope of restricting it to two
73:56 

73:56 is to make sure that we are identifying
73:58 

73:58 the most important because if we give
73:60 

73:60 people the opportunity to say
74:01 

74:01 something's important. I think all these
74:02 

74:02 things are important but to be able to
74:04 

74:04 prioritize
74:06 

74:06 um the things that are most critical
74:08 

74:08 right now is really helping us
74:09 

74:09 understand where that sits.
74:11 

74:11 All right. So, looks like we're having a
74:14 

74:14 couple more people responding now.
74:17 

74:17 Roger, do you want to move on or should
74:19 

74:19 we give it another second?
74:21 

74:21 >> I think we're good. Um, will we be able
74:24 

74:24 you'll be able to come back to these
74:27 

74:27 results when we want to have discussion,
74:29 

74:29 right?
74:29 

74:29 >> Absolutely. Yeah, we'll be able to look
74:31 

74:31 at the results in aggregate later. Yep.
74:33 

74:33 >> So,
74:35 

74:35 >> all right. Next.
74:36 

74:36 >> Oh, sorry. Before you switch from that,
74:38 

74:38 I had my hand up, but I'm sure with all
74:40 

74:40 the sharing, nobody could see it. Uh, I
74:42 

74:42 want to just add here, you know, yeah,
74:44 

74:44 the change management part is a big part
74:45 

74:45 of it, but I think in some respects,
74:49 

74:49 um, at least from what I've gleaned from
74:52 

74:52 some of our change efforts is there's
74:54 

74:54 people that are willing and ready to
74:56 

74:56 change, but they don't know what we're
74:58 

74:58 changing. So, one, it's a support of
75:01 

75:01 people that are the willingness to
75:02 

75:02 change, and then the other is
75:04 

75:04 >> what is the change? And when there's so
75:06 

75:06 many, you know, different methods or
75:08 

75:08 different paths and people are looking
75:11 

75:11 for consistency, but when we have a lot
75:14 

75:14 of people trying to decide it, we don't
75:15 

75:15 get the same consistency. So, I just
75:18 

75:18 wanted to voice that that you're right
75:20 

75:20 with these options coming up of being
75:22 

75:22 changed. But I think sometimes it's the
75:23 

75:23 uncertainty in what exactly you're
75:25 

75:25 changing, not that people aren't willing
75:27 

75:27 to change either.
75:29 

75:29 >> That's a really important clarification.
75:31 

75:31 I appreciate that feedback. And I think
75:32 

75:32 a big part of change management is
75:34 

75:34 establishing those workflows and those
75:36 

75:36 processes. And so, you know, I think
75:38 

75:38 most people are excited about the
75:40 

75:40 progress, you know, to move towards
75:42 

75:42 digital delivery. But to all the reasons
75:45 

75:45 that you've mentioned, there can be
75:47 

75:47 barriers. And so change management aims
75:49 

75:49 to address all of that, right? Building
75:51 

75:51 the workflows, building the processes,
75:53 

75:53 the leadership by buyin, the action
75:55 

75:55 plans, the priority setting. And so all
75:58 

75:58 of those things um become critical as
76:01 

76:01 you look at change management as a
76:02 

76:02 broader bucket. So that's really really
76:04 

76:04 good feedback. Thank you.
76:08 

76:08 All right, let me jump to the next one.
76:11 

76:11 So how would you describe your
76:12 

76:12 organization's position in its digital
76:14 

76:14 delivery journey?
76:17 

76:17 So we'll leave this on here and there
76:19 

76:19 are a few um opportunities um and
76:22 

76:22 options for you to look at as well. And
76:25 

76:25 really the reason why we're asking this
76:26 

76:26 is this should be very familiar. If you
76:29 

76:29 were at I HEAP we asked the same
76:30 

76:30 question as well. So this is meant to
76:32 

76:32 mirror the original question. Um but
76:35 

76:35 looking at it now compared to before
76:37 

76:37 it's giving us a chance to show any
76:38 

76:38 movement or like I said stagnation or
76:41 

76:41 are we seeing acceleration in any areas
76:43 

76:43 since um efforts that began last fall
76:46 

76:46 fall as well. So some of the options is
76:49 

76:49 no formal digital delivery efforts yet.
76:52 

76:52 A lot of people it looks like are in the
76:53 

76:53 e early exploration and pilot phases.
76:56 

76:56 Um some folks are actively implementing
76:59 

76:59 across select projects. Less so so far.
77:03 

77:03 It looks like not as many um are scaling
77:06 

77:06 digital delivery broadly.
77:23 

77:23 So somewhat consistent with what we saw
77:25 

77:25 last year.
77:36 

77:36 We've got a few more responses coming
77:37 

77:37 in.
77:48 

77:48 We definitely have a lot more
77:49 

77:49 participation at this meeting, Mona.
77:52 

77:52 >> Yes, we do. This is fantastic. It's
77:53 

77:53 good.
77:57 

77:57 All right, we've got 96 responses.
77:59 

77:59 That's great. 97. It keeps ticking up,
78:01 

78:01 so we'll just hold it here for just a
78:02 

78:02 second longer.
78:04 

78:04 >> Can we get a 100?
78:05 

78:05 >> Can we get to 100? Yes.
78:08 

78:08 >> 99. We're almost there. One more person.
78:10 

78:10 Let's do this.
78:13 

78:13 Yes,
78:15 

78:15 thank you.
78:17 

78:17 So again, the results are coming in very
78:19 

78:19 consistent that most of you are in the
78:22 

78:22 early exploration and pilot phases um or
78:24 

78:24 you're just actively implementing across
78:26 

78:26 key programs or select projects.
78:29 

78:29 Very few of you don't have a formal
78:31 

78:31 digital delivery effort yet and even
78:33 

78:33 fewer scaling digital delivery across
78:35 

78:35 your programs.
78:38 

78:38 All right. So, I'm going to give it five
78:40 

78:40 seconds and then I'll move on to the
78:42 

78:42 next question.
78:45 

78:45 All right. So, the pace of digital
78:46 

78:46 delivery activity in my organization or
78:49 

78:49 project, has it slowed, stayed the same,
78:51 

78:51 slightly increased? Has it increased
78:53 

78:53 significantly? Has it accelerated
78:56 

78:56 rapidly?
78:58 

78:58 And the reason why we're asking this
78:60 

79:00 question in this way is really helping
79:02 

79:02 us to reframe the progress. Again, I
79:04 

79:04 like to talk about velocity, not
79:06 

79:06 necessarily maturity. Um, and I think
79:08 

79:08 velocity helps us understand more
79:10 

79:10 honestly where we all are. Um, you know,
79:18 

79:18 so that's good to see. Some are slightly
79:19 

79:19 increasing, increasing significantly,
79:21 

79:21 accelerating rapidly. Wow, that's big. I
79:24 

79:24 like that.
79:26 

79:26 A few of you say that you've slowed. I'd
79:28 

79:28 be so curious to hear feedback on why
79:30 

79:30 that's happening.
79:36 

79:36 Is it organizational? Is it technology,
79:38 

79:38 you know, driven? Is it some of the
79:41 

79:41 reasons that the team has mentioned here
79:43 

79:43 earlier that people want to change, but
79:45 

79:45 then the processes aren't there or the
79:49 

79:49 priorities aren't set? Clearly, funding
79:51 

79:51 maybe could be a barrier.
79:57 

79:57 >> All right. Can we get to one? Anybody
79:59 

79:59 brave enough to to say about what
80:01 

80:01 happened
80:05 

80:05 or willing.
80:10 

80:10 So
80:12 

80:12 Mona I as many on this call who know me
80:14 

80:14 I am not afraid to come off and say
80:17 

80:17 stuff
80:18 

80:18 >> great. uh it you know I actually
80:22 

80:22 answering this question I struggled I
80:24 

80:24 think overall the program like we've
80:25 

80:25 actually slightly increased but on
80:27 

80:27 certain projects in certain areas we
80:29 

80:29 have been finding it's been slowing but
80:31 

80:31 that might also be given when we took on
80:34 

80:34 initiative to advance digital delivery
80:37 

80:37 where we were at a starting point where
80:39 

80:39 in certain aspects we were already doing
80:41 

80:41 a little bit of modeling and digital
80:44 

80:44 information but ultimately we would dumb
80:48 

80:48 it down at the end of a project and so
80:49 

80:49 we would lose some consistency on that.
80:51 

80:51 So now on certain projects where it
80:55 

80:55 comes to you're going to progress that
80:57 

80:57 through the end of a project and provide
80:59 

80:59 that information uh the slowing could be
81:02 

81:02 that it's more detailed work and so if
81:06 

81:06 you had started some initial digital
81:08 

81:08 efforts early on the slowing might be
81:11 

81:11 more project focused maybe not from a
81:13 

81:13 program focused um that is
81:17 

81:17 you know you're just seeing that the
81:19 

81:19 projects because of a lack of training,
81:23 

81:23 a you know, educational the the um the
81:27 

81:27 improvement gap that has to happen that
81:30 

81:30 some of the staff it's like it might be
81:31 

81:31 slowing a project down, but ultimately
81:33 

81:33 you're getting a better product at the
81:34 

81:34 end. So, at least that's one viewpoint
81:37 

81:37 that we have experienced on some
81:38 

81:38 projects, but I I didn't actually check
81:41 

81:41 slow, so somebody else might have to
81:43 

81:43 actually answer that one.
81:46 

81:46 >> That's great feedback. Thank you so much
81:48 

81:48 for weighing in. I see Jacob has his
81:50 

81:50 hand up. I'm not sure.
81:52 

81:52 >> Yeah, I I do have my hand up and I
81:54 

81:54 wanted to kind of add on to what Devin
81:57 

81:57 was talking about. We've we've seen ours
81:59 

81:59 at Tex Dot really increase rapidly. Uh
82:02 

82:02 we accelerated rapidly. Uh but that came
82:05 

82:05 from really um our administration really
82:09 

82:09 starting to find value in this and
82:11 

82:11 really starting to mandate that our
82:13 

82:13 districts participate. And so, uh, if
82:16 

82:16 when we talked at IHEA, uh, we had like
82:19 

82:19 eight pilot projects. Uh,
82:21 

82:21 consequentially, the next week we had
82:23 

82:23 our, uh, Texas, uh, statewide
82:25 

82:25 transportation conference. And at that
82:28 

82:28 conference, our executive director
82:30 

82:30 mandated that every district have a
82:32 

82:32 pilot project that lets by the end of
82:34 

82:34 2027.
82:36 

82:36 And so, we went from eight pilot
82:38 

82:38 projects to like almost 40 pilot
82:41 

82:41 projects in the matter of months. And so
82:44 

82:44 we are now accelerated rapidly and we
82:47 

82:47 are uh really
82:50 

82:50 finding it find it difficult to keep up
82:53 

82:53 with the things that to Devon's point
82:54 

82:54 the training and all that stuff like
82:56 

82:56 that. We've really had to ramp up our
82:58 

82:58 our thought process on how are we going
82:60 

82:60 to get this proper training to all of
83:02 

83:02 the folks that need this across the 25
83:05 

83:05 districts and in all of our area offices
83:07 

83:07 and construction part of it and all
83:08 

83:08 these different parts of it. So just
83:10 

83:10 wanted to share that little tidbit. Um
83:14 

83:14 Thank you so much, Jacob. Yeah, I mean,
83:16 

83:16 the pace of, you know, there's always a
83:18 

83:18 risk when you grow so fast, so quickly
83:20 

83:20 that there are pieces such as training
83:22 

83:22 that need to really be in place or need
83:24 

83:24 to catch up um to keep up with the pace
83:26 

83:26 of growth. So it is also really
83:28 

83:28 interesting where you talk about like
83:30 

83:30 the mandate you know I I can't remember
83:32 

83:32 who mentioned that but you know that
83:34 

83:34 sort of leadership requirement makes it
83:38 

83:38 it almost forces our hands to make this
83:39 

83:39 a priority and to find solutions and to
83:42 

83:42 begin to prioritize how we take on
83:44 

83:44 digital delivery at a bigger level. So,
83:47 

83:47 it's it's good to see that more leaders
83:49 

83:49 are seeing the value in this and you
83:50 

83:50 know that direction is becoming more and
83:52 

83:52 more clear um across the
83:56 

83:56 >> it really does help with the messaging
83:58 

83:58 right to your point Mona it it's we were
84:00 

84:00 fighting a little bit of well we don't
84:03 

84:03 really see the value in that and we're
84:05 

84:05 not really going to do that in our
84:06 

84:06 district and our contractors don't want
84:08 

84:08 it or these are all things that we heard
84:10 

84:10 and now that our executive director has
84:12 

84:12 come out it's like there's not that
84:14 

84:14 conversation anymore. It's more of well,
84:17 

84:17 how are we going to do this? What
84:19 

84:19 assistance do we need? This is the
84:21 

84:21 direction we're going. So that that
84:23 

84:23 leadership buyin is really really
84:25 

84:25 critical.
84:26 

84:26 >> Fantastic. Yep. All right. I'm going to
84:28 

84:28 move on to the next question.
84:30 

84:30 >> Oh, sorry Mona. I did
84:32 

84:32 >> I did want to just also um like add on
84:35 

84:35 to something Jacob said that I didn't
84:36 

84:36 think about until I heard him say it.
84:38 

84:38 Um, we've experienced a similar thing in
84:41 

84:41 Calrans where we have a lot of
84:43 

84:43 leadership and people who are excited
84:45 

84:45 about this, but we are not able to keep
84:49 

84:49 up with the demand when it comes to the
84:51 

84:51 support services to expand it to
84:54 

84:54 something that is more robust. And so
84:57 

84:57 the program has stayed fairly small in
84:59 

84:59 where we have targeted effectiveness.
85:01 

85:01 namely because we everybody sees the
85:04 

85:04 value, everybody sees the benefit,
85:05 

85:05 everybody sees the direction, but we
85:07 

85:07 don't have everything figured out and we
85:09 

85:09 don't have the self-sufficiency in place
85:11 

85:11 yet that is allowing people to take it
85:15 

85:15 and run with it. So that that
85:17 

85:17 development of those support services
85:19 

85:19 is, you know, I guess not allowing it to
85:22 

85:22 increase as significantly as it could
85:24 

85:24 and in some cases might be slowing.
85:26 

85:26 >> That's really interesting. So, is it
85:28 

85:28 support services internally through
85:29 

85:29 staff? Like, you just don't have the
85:31 

85:31 resources to ramp up or is it contractor
85:33 

85:33 service?
85:34 

85:34 >> Yeah,
85:34 

85:34 >> that seems to be consistent with a lot
85:36 

85:36 of what I'm hearing is we've got the
85:37 

85:37 pilots, we want to do it, but we don't
85:39 

85:39 have the people to get it done.
85:41 

85:41 >> And, you know, you've got a lot of DOS
85:43 

85:43 on here. Uh, I don't know how many other
85:45 

85:45 DOS have the structure that Calrans has
85:49 

85:49 where we still do 90% of our work in
85:51 

85:51 house. So, you know, we still have 90%
85:54 

85:54 of our design and construction work is
85:56 

85:56 done with state resources. So, that
85:58 

85:58 means we've got a whole host of state
85:60 

85:60 staff that have to have that
86:02 

86:02 headquarters and process support, have
86:04 

86:04 the or you know, the standards
86:06 

86:06 development in that. It's not something
86:08 

86:08 by our organizational structure that we
86:11 

86:11 could farm out to folks that have maybe
86:13 

86:13 already been experts in this. We've got
86:14 

86:14 to kind of build that expertise from
86:16 

86:16 within. And so when you've got a big
86:19 

86:19 program, but you've got a staff of like
86:22 

86:22 10 people in the department that are
86:24 

86:24 supporting all the projects when they
86:25 

86:25 need to know what's different, it's it's
86:27 

86:27 hard to, you know, I I added a comment
86:30 

86:30 to the mural board that yeah, the
86:32 

86:32 funding and the support structure,
86:34 

86:34 especially when budgets are low, it's
86:36 

86:36 hard to get that level of support
86:38 

86:38 necessary to keep the project staff
86:42 

86:42 effectively doing what they need to do.
86:44 

86:44 >> Yeah, that makes sense. Very good
86:47 

86:47 feedback. Thank you. And for everyone
86:49 

86:49 else, please don't be shy. Add your
86:51 

86:51 comments in. Raise your hand. Jump in
86:53 

86:53 while we're doing this. I'd love to hear
86:54 

86:54 from all of you. All right. So, next
86:57 

86:57 question is, which drivers have become
86:58 

86:58 more important for advancing digital
87:00 

87:00 delivery in your organization? So, here
87:03 

87:03 you can pick your top three. I know all
87:05 

87:05 of these are important to some degree,
87:07 

87:07 but we want to start to understand, you
87:09 

87:09 know, where you're prioritizing um your
87:12 

87:12 efforts and um you know, it would really
87:15 

87:15 start to understand the shifts in some
87:17 

87:17 of these primary drivers.
87:21 

87:21 And so it's not about reasking what
87:23 

87:23 matters. It's really like we're really
87:25 

87:25 asking like what's intensified for you
87:26 

87:26 this year compared to, you know, fourth
87:29 

87:29 quarter, third quarter last year.
87:38 

87:38 And so for folks who are saying other,
87:40 

87:40 I'd love to hear whether it's in the
87:42 

87:42 chat or if you can unmute and share with
87:44 

87:44 us what would be the other.
88:10 

88:10 Okay, I see faster delivery or quicker
88:12 

88:12 pace. Okay, thanks, Ben.
88:24 

88:24 So quality and consistency I think that
88:26 

88:26 that is the front runner. So far we've
88:28 

88:28 got 96 people who have responded so far.
88:30 

88:30 Can we make it to 100?
88:34 

88:34 Better decision making, efficiency and
88:37 

88:37 cost. So efficiency, cost savings,
88:38 

88:38 improved uh collaboration and better
88:41 

88:41 decision- making are sort of almost tied
88:45 

88:45 for second here.
88:47 

88:47 less on regulatory and compliance.
88:50 

88:50 Consistent with the results of the other
88:51 

88:51 question,
88:53 

88:53 safety and risk doesn't seem as much of
88:55 

88:55 a concern, although it's there.
89:07 

89:07 So, I'll read Taylor's feedback. Jacob
89:09 

89:09 probably has more insight on this than
89:11 

89:11 me, but my impression is Texas DOT
89:13 

89:13 administration wants to be one of the
89:14 

89:14 national leaders in digital delivery,
89:16 

89:16 which is one of the drivers. That's
89:18 

89:18 fantastic.
89:24 

89:24 Interoperable data sets. Thanks, Matt.
89:26 

89:26 That's um good perspective.
89:30 

89:30 So, interoperability is critical.
89:38 

89:38 All right. Any thoughts or questions on
89:39 

89:39 this one as we finalize uh the feedback
89:42 

89:42 here,
89:51 

89:51 >> you know,
89:52 

89:52 >> um hey, just to point out to
89:56 

89:56 um Devin and Jacob, I tried to capture
89:59 

89:59 what they were talking about in a note
90:01 

90:01 in Mural. Um it it's in there where it
90:05 

90:05 says meant to meter comments. So just
90:08 

90:08 fix it if it's wrong or say something if
90:10 

90:10 you else if you feel like it.
90:13 

90:13 >> So it's interesting. So Jonathan, you
90:15 

90:15 said the cost savings is important. Um
90:17 

90:17 though it's very challenging to get
90:19 

90:19 actual cost savings figures. We're
90:20 

90:20 working on some of this right now with
90:22 

90:22 the Michigan Department of
90:23 

90:23 Transportation where we're trying to
90:24 

90:24 quantify the cost of staying the same
90:27 

90:27 versus the cost of change. And it is a
90:30 

90:30 difficult number to get to, but there is
90:33 

90:33 a process that you can work through that
90:34 

90:34 can help achieve that. Um and sometimes
90:37 

90:37 there is a ramp up cost or a ramp up in
90:39 

90:39 time both hard and soft cost. So as you
90:42 

90:42 begin to deploy
90:44 

90:44 um these pilots or start to advance
90:46 

90:46 digital delivery, initially it may feel
90:49 

90:49 like more time, more cost, more
90:51 

90:51 training, more you know resources and
90:53 

90:53 effort, but the long-term gain I think
90:56 

90:56 is more efficiencies you know and all of
90:58 

90:58 the you know benefits that we know
90:60 

90:60 digital delivery can bring to um
91:03 

91:03 national and state DOS.
91:09 

91:09 >> It's all very good feedback. Thank you.
91:12 

91:12 Any other verbal comments that anybody
91:14 

91:14 wants to make? I see Will, you're on
91:16 

91:16 your hand is raised.
91:17 

91:17 >> Yeah. Hi. Um I will say that there are
91:21 

91:21 um there there is ROI stuff that is
91:25 

91:25 being put out by building smart
91:27 

91:27 international.
91:29 

91:29 Uh so some of your international peers
91:32 

91:32 have it's not specific just to do but
91:35 

91:35 but there certainly is value. Um
91:39 

91:39 Singapore has seen tremendous savings in
91:41 

91:41 in time and cost and efficiency and so
91:45 

91:45 they've embraced it uh wholeheartedly.
91:47 

91:47 So you can find international examples.
91:53 

91:53 Yeah, that that's a good point. Um, will
91:55 

91:55 I highlight a study from the UK that is
91:59 

91:59 pretty transferable to the US? I think
92:02 

92:02 um unlike maybe well no I won't say
92:05 

92:05 unlike but um is pretty transferable to
92:08 

92:08 the US. So I'll I have that thing. I'll
92:11 

92:11 find the link to it and share it um
92:16 

92:16 somehow in when I get a minute here.
92:18 

92:18 Yes.
92:20 

92:20 >> All right. So I'm going to move on to
92:21 

92:21 the next question here. question is
92:23 

92:23 which barriers are getting easier to
92:25 

92:25 manage since last year. So here you can
92:28 

92:28 select up to three and there's a lot of
92:29 

92:29 options. So I'll start to read some of
92:31 

92:31 them because it is a little smaller on
92:33 

92:33 the screen. So first one is limited
92:35 

92:35 executive leadership support. I think
92:36 

92:36 we've already talked about that.
92:38 

92:38 Resistance to change is the second one.
92:40 

92:40 Technology investment costs. Um
92:43 

92:43 standards and interoperability
92:45 

92:45 challenges. Data governance challenges.
92:47 

92:47 So really it's around ownership and
92:49 

92:49 stewardship. um data steward resistance,
92:53 

92:53 data security and privacy concerns. You
92:55 

92:55 know, we hear this quite a bit around AI
92:57 

92:57 as well as you know that is a a limiter
93:00 

93:00 um specifically for AI skills and
93:03 

93:03 training gaps. We've talked about that.
93:05 

93:05 Increased awareness that's quickly
93:07 

93:07 becoming the top one so far. Awareness
93:09 

93:09 is really leading right now.
93:20 

93:20 And so what we're trying to do by
93:21 

93:21 comparing this to the survey results
93:23 

93:23 that we had last year is I really, you
93:26 

93:26 know, we're hoping to create a sort of
93:27 

93:27 before and after narrative without
93:29 

93:29 rerunning the entire survey, right? So,
93:32 

93:32 you know, um this will help us
93:35 

93:35 understand what's getting easier based
93:37 

93:37 on some of the challenges you've had
93:39 

93:39 before.
93:45 

93:45 Mona while the results are coming in um
93:48 

93:48 the previous question with the we were
93:51 

93:51 talking about the efficiencies there's
93:53 

93:53 another uh study that um was where we
93:56 

93:56 started uh and it's the information
93:58 

93:58 coming out of Norway of what they have
93:60 

93:60 learned of how uh BIM has helped them on
94:03 

94:03 the projects where they've um
94:05 

94:05 implemented it and these numbers are
94:07 

94:07 very rough but they're numbers that have
94:09 

94:09 stuck in my head so just for like you
94:11 

94:11 know aware awareness of the group. Uh
94:13 

94:13 they found that on projects where they
94:15 

94:15 use BIM, they saw a reduction in 90% uh
94:19 

94:19 90% of change orders and an average
94:22 

94:22 overrun went from like roughly 20% of a
94:24 

94:24 cost overrun down to like 3 to 7% cost
94:27 

94:27 overrun. So it's you know what they were
94:29 

94:29 showing was really that you're still
94:31 

94:31 going to have change. there's the
94:32 

94:32 unknowns, but they were ultimately
94:34 

94:34 eliminating the things that could have
94:36 

94:36 been proactively resolved and your cost
94:38 

94:38 increases over the course of a project
94:41 

94:41 were reduced. So, um, but yeah, like
94:45 

94:45 we've also seen the same thing where
94:46 

94:46 it's going to be some more time in to
94:48 

94:48 get that benefit and then helping people
94:50 

94:50 to understand that story that you're
94:52 

94:52 going to find some efficiencies. You're
94:53 

94:53 going to find some improvements in your
94:55 

94:55 process flows and how you know how
94:57 

94:57 quickly you get through something, but
94:58 

94:58 you might still spend more time in your
95:00 

95:00 design and planning phase, but you're
95:02 

95:02 looking at a project as a whole like how
95:04 

95:04 are you getting efficiency overall and
95:06 

95:06 then how does that play into that better
95:08 

95:08 decision for the future. So there's
95:10 

95:10 another study there that um or a set of
95:13 

95:13 information that they have shared, but
95:15 

95:15 if you get the information from them,
95:17 

95:17 it's in Norwegian and they don't have a
95:19 

95:19 English translation, so it's kind of
95:21 

95:21 hard to get the the proper information
95:23 

95:23 from their translation, too.
95:26 

95:26 >> That's funny. Well, there's a lot we can
95:28 

95:28 learn from each other. That's why we're
95:30 

95:30 here to talk. And there's a lot that we
95:32 

95:32 can learn from transportation agencies,
95:35 

95:35 you know, abroad and around the world.
95:37 

95:37 Um, and that's really helpful. If you
95:39 

95:39 have a link to that study, maybe uh,
95:41 

95:41 yeah, try Google Translate or chat GPT
95:43 

95:43 translate. That might be really good.
95:45 

95:45 Um, but you could drop the link inside
95:47 

95:47 of the chat here if others want to take
95:48 

95:48 a look at it as well or put it inside of
95:50 

95:50 the mural board. That's a really helpful
95:51 

95:51 resource.
95:52 

95:52 >> Yeah, I'll have to uh I'll have to
95:55 

95:55 search for from one of my old staff who
95:57 

95:57 found that and had that conversation
95:58 

95:58 with them.
95:59 

95:59 >> Sounds good. So, Randall says costs are
96:02 

96:02 should be basically irrelevant. Digital
96:04 

96:04 delivery should only be about delivering
96:06 

96:06 a better final product that we can
96:08 

96:08 maintain and manage in the long term.
96:15 

96:15 >> Well, I think um that that's an
96:17 

96:17 interesting comment. You know, this
96:19 

96:19 always comes up. What's the RAI on this?
96:21 

96:21 How do we prove it? But, you know, you
96:24 

96:24 can't just stand still. And clearly,
96:27 

96:27 using tools and processes and always
96:30 

96:30 improving them is what you need to do.
96:33 

96:33 So, it's a little bit of a elusive goal
96:37 

96:37 to say you're going to identify ROI real
96:40 

96:40 conclusively. Um, but you can do
96:44 

96:44 specific studies, I guess, and get some
96:47 

96:47 support for what's needed to convince
96:50 

96:50 people to not stand still.
96:54 

96:54 >> Yeah. And it looks like I mean
96:55 

96:55 overwhelmingly increased awareness is uh
96:59 

96:59 a barrier that's you know um becoming
97:03 

97:03 easier to manage. So that's great.
97:04 

97:04 Awareness is really the first step here.
97:08 

97:08 Limited executive leadership support
97:10 

97:10 resistance to change look like those are
97:11 

97:11 the second two. So that seems pretty
97:14 

97:14 consistent with the things that we've
97:15 

97:15 been hearing as well.
97:17 

97:17 >> All right. So I'm going to um jump to
97:20 

97:20 the next question. So, you know, in the
97:23 

97:23 prior question, we talked about what's
97:24 

97:24 getting easier. Now, it's the same, you
97:28 

97:28 know, items that you can select for.
97:29 

97:29 What is becoming more difficult?
97:35 

97:35 I know a lot are becoming more
97:36 

97:36 difficult, but if you had to prioritize,
97:38 

97:38 you know,
97:50 

97:50 All
97:59 

97:59 right. So, I'm seeing technology
98:00 

98:00 investment costs coming up there and
98:02 

98:02 data governance.
98:07 

98:07 A lot of the conversation has been
98:09 

98:09 around change management. So, it's
98:10 

98:10 interesting to see the tech itself and
98:13 

98:13 governance itself becoming something
98:15 

98:15 that's challenging.
98:20 

98:20 Does anybody want to maybe unmute or
98:22 

98:22 drop anything in the chat to help add
98:24 

98:24 any color to if anybody responded with
98:26 

98:26 technology investment costs or data
98:27 

98:27 governance? Is there anything that you
98:29 

98:29 want to share that would explain why you
98:31 

98:31 think that is or you know some ideas
98:33 

98:33 that you have on how that's being
98:35 

98:35 managed? Katie?
98:38 

98:38 Yeah, I would say with the technology
98:40 

98:40 investment, there's so much technology
98:44 

98:44 out there right now and it's coming at
98:46 

98:46 us so fast. It can be really hard to
98:50 

98:50 sift through all of the different things
98:53 

98:53 that are out there and try to put
98:55 

98:55 together a technology stack that works
98:57 

98:57 for you. And then of course as soon as
98:60 

98:60 you do put some things together like
99:02 

99:02 more new features come on and um then
99:06 

99:06 trying to figure out how those fit
99:08 

99:08 together or you might have some legacy
99:10 

99:10 apps. How does that fit with new stuff
99:13 

99:13 coming in or do we have to transfer all
99:16 

99:16 of this leg legacy stuff to new apps and
99:19 

99:19 then how do you move that data or where
99:22 

99:22 you keeping old data? What are you doing
99:23 

99:23 with new data? It starts to become very
99:25 

99:25 complex pretty fast.
99:29 

99:29 Yeah, thank you for that feedback,
99:30 

99:30 Katie. I can understand and see that. I
99:32 

99:32 wonder if having more specific guidance
99:34 

99:34 on how to select the right technology
99:35 

99:35 could be helpful, right? Like almost
99:38 

99:38 like a checklist or like a short
99:39 

99:39 document that is the, you know,
99:42 

99:42 technology procurement guide and maybe a
99:46 

99:46 process that DOS can follow to help them
99:48 

99:48 through that decision matrix. I think
99:51 

99:51 that that would be some helpful
99:53 

99:53 information, but I I think oftentimes
99:55 

99:55 DOTs are going to be
99:58 

99:58 presented with a a unique challenge each
100:00 

100:00 time, too. Um, you know, so having some
100:02 

100:02 basic information to help tell that
100:04 

100:04 story. Uh, we're going through the
100:07 

100:07 process of putting together everything
100:09 

100:09 for the selection of a common data
100:11 

100:11 environment right now. Um, so we, you
100:13 

100:13 know, there's also whatever the state
100:14 

100:14 requirements are, you have to work
100:15 

100:15 through for your procurement, making
100:17 

100:17 sure you're justifying it. But then the
100:19 

100:19 investment part oftentimes that like I
100:23 

100:23 agree with everything was Katie was
100:24 

100:24 saying, it's hard to develop that
100:25 

100:25 technology stack, but then how do you
100:27 

100:27 justify it to the budget people that you
100:31 

100:31 need to work with for these increased
100:34 

100:34 investments? Then if you come to them
100:36 

100:36 and say we need two pieces of software
100:38 

100:38 that offer the same functionality but
100:40 

100:40 they're important to have for different
100:41 

100:41 phases of a project. How do we sell that
100:45 

100:45 when we're basically doubling the cost
100:47 

100:47 to get all the efficiency and benefit
100:48 

100:48 out of it? you know, so it maybe it does
100:51 

100:51 lead back to the ROI of when it comes to
100:55 

100:55 getting the budgetary approval when you
100:58 

100:58 have to go to doof to ask for more money
101:01 

101:01 or you know who whoever your financial
101:03 

101:03 group is to ask for more money to cover
101:05 

101:05 this if you don't have it within your
101:06 

101:06 budget.
101:08 

101:08 How does the overall process that you're
101:10 

101:10 trying to establish the standards and
101:13 

101:13 then that supports the fact that you
101:16 

101:16 like no one tool is going to help you
101:17 

101:17 solve this?
101:19 

101:19 >> That's really great feedback. Fantastic.
101:21 

101:21 Yes. Yeah. Building the ROI
101:26 

101:26 for any short-term investment or upfront
101:28 

101:28 investment that you make compared with
101:31 

101:31 the long-term savings, I think, is going
101:32 

101:32 to be really critical as you get buyin
101:34 

101:34 from the leadership. I want to draw our
101:36 

101:36 attention to one comment that let me see
101:39 

101:39 where is it. Is it just Baker? An option
101:41 

101:41 missing from the question is how to
101:43 

101:43 protect design IP. That's a good one. Um
101:45 

101:45 as we move towards digit digitization.
101:49 

101:49 Um and she says I'm curious how others
101:51 

101:51 handle clients asking for digital files
101:53 

101:53 models of the final design. How do you
101:55 

101:55 protect that IP? Is there anybody that
101:57 

101:57 can weigh in on that?
102:00 

102:00 Any thoughts from our panel? Will,
102:02 

102:02 Katie, Jacob, Devin, others.
102:09 

102:09 >> And we put Allan on the spot. Haven't
102:10 

102:10 you guys dealt with this, Allen, in uh
102:13 

102:13 in your project with that you've moved
102:15 

102:15 to model as a legal deliverable?
102:27 

102:27 That one's still here. Um,
102:31 

102:31 >> I am I just got back. Sorry. I stepped
102:34 

102:34 away from my computer for a minute.
102:36 

102:36 >> That's what you get. We caught you, Al.
102:38 

102:38 >> I know you caught me when I walked away
102:40 

102:40 real quick.
102:42 

102:42 >> I promise I don't have a camera in your
102:44 

102:44 office or anything.
102:45 

102:45 >> I I got you.
102:48 

102:48 >> So, the question Jess Baker shared a
102:50 

102:50 comment that says, "An option that's
102:52 

102:52 missing from our survey is how to
102:53 

102:53 protect design IP as we move towards
102:56 

102:56 digital delivery." So, she's curious,
102:58 

102:58 how do others handle clients asking for
102:60 

102:60 digital files and models of the final
103:02 

103:02 design? How to protect that IP? And um
103:06 

103:06 do you have anything that you want to
103:07 

103:07 add or
103:08 

103:08 >> as far as you know IP? So, your
103:10 

103:10 intellectual property uh you know, if
103:13 

103:13 you think about it, the uh consultants
103:16 

103:16 and stuff that are doing work for the
103:18 

103:18 DOT, uh that's really our ultimately our
103:21 

103:21 property. That's that's what we're
103:22 

103:22 paying for. Uh so we're working towards
103:26 

103:26 that you know common data environment
103:29 

103:29 where we have most of our consultants or
103:32 

103:32 getting most of our consultants into our
103:35 

103:35 projectwise environment. Uh so as
103:38 

103:38 they're working on that we have you know
103:41 

103:41 a workspace state kit that they're also
103:44 

103:44 utilizing that we're providing. Uh so we
103:48 

103:48 also have multiple groups working with
103:51 

103:51 our ACE and so forth. So as we build out
103:55 

103:55 this workspace it is locked down. Uh
103:58 

103:58 there is you know the ability to request
104:02 

104:02 to get stuff into that workspace because
104:04 

104:04 as we are building the workspace and
104:07 

104:07 building out uh you know additional uh
104:10 

104:10 features or layers levels and and so
104:13 

104:13 forth we need to have that controlled.
104:16 

104:16 Uh so with controlling that um you know
104:20 

104:20 we're able to automate and develop items
104:24 

104:24 to you know check these projects and so
104:27 

104:27 forth. So there's not, you know,
104:28 

104:28 consultant A does it one way, consultant
104:31 

104:31 B does it uh another. Uh it's consistent
104:35 

104:35 across the board. Uh so, you know, we do
104:39 

104:39 share out all of that information and we
104:41 

104:41 share it between you know consultants as
104:44 

104:44 well as consultant A or B, hey, we need
104:47 

104:47 you know this this cell developed or
104:50 

104:50 whatever. We're bringing that into our
104:52 

104:52 environment, putting that into the
104:54 

104:54 environment and then everybody can is
104:56 

104:56 able to use that. Uh so there's no need
104:60 

104:60 for anybody to create their own
105:04 

105:04 workspaces
105:05 

105:05 uh as they're able to utilize you know
105:08 

105:08 the DO's uh you know workspace and
105:11 

105:11 information. So that's how uh we're
105:14 

105:14 dealing with that you know intellectual
105:17 

105:17 property.
105:18 

105:18 >> Thanks so much Alan.
105:21 

105:21 You know, Curtis said that perhaps a
105:23 

105:23 matrix to address the connectivity
105:25 

105:25 required. Let me see. You guys are
105:28 

105:28 dropping in so many comments. It's
105:29 

105:29 scrolling up. I lost that comment.
105:33 

105:33 To ensure an app and any app is capable
105:35 

105:35 of plugging into the main data
105:36 

105:36 infrastructure and deliver the minimum
105:37 

105:37 requirements, preferably the maximum
105:39 

105:39 requirements. Very good feedback. Thank
105:42 

105:42 you all for dropping all these great
105:43 

105:43 comments in. And I know that um we'll be
105:46 

105:46 able to capture all of this. Roger. This
105:48 

105:48 is just for us and Rockley to keep an
105:50 

105:50 eye on that all of these comments we
105:52 

105:52 should move over to Mural.
105:56 

105:56 >> Yeah,
105:57 

105:57 >> Mona just I just want to highlight I saw
105:60 

106:00 a couple of hands pop up in the
106:02 

106:02 attendees but they went down. So um I
106:05 

106:05 was trying to find a place to interject
106:08 

106:08 but if there's anybody that's you know
106:10 

106:10 not a panelist who wanted to raise their
106:13 

106:13 hand and we can figure out how to patch
106:16 

106:16 you in. I think I saw Andy was one and
106:20 

106:20 there was another one. But don't don't
106:22 

106:22 let us discourage your dialogue. If you
106:24 

106:24 have something you want to contribute,
106:26 

106:26 raise your hand and we'll find a way to
106:28 

106:28 to
106:29 

106:29 get you voice.
106:33 

106:33 >> I see two hands up or one.
106:37 

106:37 So Gary uh Rackley, can you help us get
106:41 

106:41 >> right? Uh and also for panel if you're
106:43 

106:43 finished speaking please lower your hand
106:45 

106:45 because it will obscure I think the
106:47 

106:47 problem is that um it's obscuring other
106:49 

106:49 members um from us recognizing it and so
106:53 

106:53 when you're finished speaking if you
106:54 

106:54 would just lower your hand um I can do
106:56 

106:56 it for you but um anyways yes Gary
107:01 

107:01 >> so
107:02 

107:02 uh you asked uh technology investment
107:06 

107:06 costs how that was becoming more
107:08 

107:08 difficult really for the state of Oregon
107:10 

107:10 we're just going through a really hard
107:12 

107:12 time with uh budgets right now. So
107:17 

107:17 any discussion where we're trying to
107:19 

107:19 spend money is basically just greeted
107:21 

107:21 with a flatout no
107:23 

107:23 >> regardless what it's going to give us.
107:30 

107:30 Yeah, that's a significant challenge
107:36 

107:36 >> on the
107:38 

107:38 >> and the driver is funding Gary just
107:40 

107:40 funding availability or grants.
107:43 

107:43 >> Yeah, the the driver is funding. Um
107:46 

107:46 basically our uh right now for instance
107:49 

107:49 in our current bienium we're $242
107:53 

107:53 million in the hole that we're looking
107:55 

107:55 for the legislature to actually either
107:58 

107:58 fix or we're going to lay off uh about
108:01 

108:01 500 employees.
108:06 

108:06 >> Yeah. the juxtaposition of managing that
108:08 

108:08 budget and our people resources compared
108:11 

108:11 to advancing something more holistic
108:13 

108:13 like digital delivery. It becomes very
108:16 

108:16 very complex at a local level. Thank you
108:18 

108:18 for sharing that Gary.
108:21 

108:21 >> Will I saw you hand up? You've been
108:23 

108:23 patient. Go ahead. Yeah, I just wanted
108:26 

108:26 to say quickly uh the infrastructure
108:28 

108:28 domain steering committee for building
108:31 

108:31 smart international is
108:34 

108:34 recently at Berlin we became more aware
108:37 

108:37 of work that needs to be done on kind of
108:40 

108:40 security to better empower that within
108:44 

108:44 uh the IFC.
108:46 

108:46 So that is something that we are
108:49 

108:49 starting to wrestle with but but I agree
108:53 

108:53 >> we do have to make sure in an open data
108:55 

108:55 environment we we have means to protect
108:58 

108:58 the data and um support model as legal
109:03 

109:03 document or delivery. So, I think that
109:07 

109:07 was it.
109:12 

109:12 >> Yep.
109:13 

109:13 >> Yeah. Going back to the IP uh
109:16 

109:16 conversation, um I wanted to add a
109:19 

109:19 little bit from a different perspective
109:20 

109:20 than Allen. Uh because I've talked with
109:23 

109:23 Allen a few times about what Pendot is
109:25 

109:25 doing and we've gotten some information
109:26 

109:26 from them to help us. Um but the one
109:30 

109:30 thing we learned from those
109:30 

109:30 conversations is yet again we have a
109:32 

109:32 complete like almost a complete inverse
109:35 

109:35 of how we have people responsible for
109:37 

109:37 delivering information. So being a
109:40 

109:40 heavily state staff focused organization
109:42 

109:42 and some unique
109:46 

109:46 professional engineer professional land
109:48 

109:48 survey laws that from what I understand
109:51 

109:51 are unique to California across the
109:53 

109:53 country. Um, that's a big that's a big
109:56 

109:56 uh point of uh uh conversation for us.
110:01 

110:01 So, up until this point, we've been
110:04 

110:04 utilizing AMG information as information
110:06 

110:06 only for quite some time. So, it goes
110:08 

110:08 out as the information handout, but our
110:10 

110:10 legal documentation still points back to
110:13 

110:13 the 2D information. So, but that's
110:15 

110:15 really mostly just surface shape file
110:17 

110:17 information that's being provided as we
110:19 

110:19 move into this world of BIM and
110:21 

110:21 delivering more information. Uh I'm not
110:24 

110:24 the expert on it from within our
110:26 

110:26 organization, but I know enough to speak
110:28 

110:28 to be dangerous. Um they are working on
110:32 

110:32 a process of for each responsible unit
110:35 

110:35 delivering information on a project. How
110:37 

110:37 do we have a lockdown of that
110:38 

110:38 information? So we've got the working
110:40 

110:40 files for staff internally and then what
110:42 

110:42 are we delivering out to industry to
110:46 

110:46 utilize and building? how do we make
110:47 

110:47 sure it's, you know, read only or it's
110:50 

110:50 not changeable or we have steps in place
110:53 

110:53 that if changes need to be made, we're
110:55 

110:55 just following a process to do that. Um,
110:57 

110:57 so for to whoever asked that question,
111:01 

111:01 um, just wanted to add a little bit more
111:03 

111:03 context.
111:06 

111:06 >> Really Deon, you're you're talking about
111:08 

111:08 locking down at a element level, right,
111:11 

111:11 within a model.
111:13 

111:13 >> Uh, yeah. Yeah.
111:18 

111:18 Yeah,
111:19 

111:19 >> for that Devon uh for you know Pendot uh
111:24 

111:24 we do lock that down as far as when we
111:26 

111:26 deliver that as as a project. So you
111:30 

111:30 know what you're signing and sealing uh
111:32 

111:32 and so forth is is basically locked
111:35 

111:35 down.
111:36 

111:36 >> Uh and we utilize what we call our
111:39 

111:39 certification memo
111:41 

111:41 >> uh to to lock that down. So you can
111:44 

111:44 download those files. Uh the contractor
111:47 

111:47 can download those files, but it comes
111:49 

111:49 with what we call um basically an MD5
111:52 

111:52 checksum. So it's about a 20omed digit
111:55 

111:55 code that's a digital fingerprint of
111:58 

111:58 that file. So as you know they download
112:01 

112:01 that our uh you know basically the
112:05 

112:05 document of record that is held within
112:08 

112:08 our system. We we host it within uh our
112:10 

112:10 project wise environment, but there's a
112:12 

112:12 link into it. If they download those
112:14 

112:14 files and there's a program set up that
112:17 

112:17 they can check their MD5 checksum, that
112:20 

112:20 digital fingerprint with ours. If it
112:23 

112:23 matches, you still have the current
112:24 

112:24 files. Ours is always the document of
112:28 

112:28 record. Uh but they can check that to
112:31 

112:31 make sure they have that. So if they
112:33 

112:33 would go in and modify that DGN any way
112:36 

112:36 that digital fingerprint changes. So we
112:39 

112:39 do lock that down. It's just on the
112:41 

112:41 design side. That's where we're sharing,
112:43 

112:43 you know, that workspace or, you know,
112:45 

112:45 state kit or whatever. We're sharing
112:47 

112:47 that, you know, with all of our
112:50 

112:50 consultants that can utilize that.
112:52 

112:52 >> Right. Right. the the part that I think
112:56 

112:56 is a little unique to us and um each
113:01 

113:01 functional group that has responsibility
113:02 

113:02 for for certain parts of it. We're also
113:05 

113:05 maybe running into that a little bit
113:07 

113:07 that even internally we have some
113:08 

113:08 intellectual property. You know, you
113:11 

113:11 can't touch my stuff. So here it is in
113:14 

113:14 view only versus how do we how do we
113:18 

113:18 then how do we work together? Y so even
113:21 

113:21 with our certification memo I have
113:24 

113:24 probably there there's a couple projects
113:26 

113:26 I have probably eight different
113:28 

113:28 signatures and seals on it
113:30 

113:30 >> but when we give that out it lists those
113:34 

113:34 different files that they're actually
113:37 

113:37 signing and sealing they're responsible
113:39 

113:39 for. So we we have that broken down as
113:42 

113:42 well.
113:42 

113:42 >> Okay.
113:44 

113:44 >> Yeah. This is this is an interesting
113:46 

113:46 maybe this is a subject for more digging
113:49 

113:49 into more in a future meeting. I know in
113:52 

113:52 the next meeting we're thinking about
113:55 

113:55 looking at um ISO 19650 and the CD
113:59 

113:59 component of it. Seems like this is
114:01 

114:01 related to that what you described
114:03 

114:03 Allen. And
114:04 

114:04 >> it does also seem like a place where
114:06 

114:06 leveraging what's working in one
114:08 

114:08 environment would help a lot of others
114:11 

114:11 to do things in a similar way as opposed
114:14 

114:14 to trying to figure it out differently
114:16 

114:16 each time or slightly differently. So
114:20 

114:20 this seems like a good topic to put on
114:22 

114:22 our list of for future or for continued
114:25 

114:25 exploration.
114:27 

114:27 >> Thanks Roger. So I'm going to move on to
114:29 

114:29 the next question in the interest of
114:30 

114:30 time. And so this part of the question,
114:33 

114:33 what is or our question series, what's
114:35 

114:35 the biggest gap between digital delivery
114:37 

114:37 vision and execution in your
114:39 

114:39 organization or projects? Um really the
114:42 

114:42 the gist of why we're asking this
114:44 

114:44 question is we're really you know now
114:46 

114:46 moving toward you know vision to
114:49 

114:49 execution and trying to set up the road
114:51 

114:51 map uh for our work together and the
114:53 

114:53 upcoming uh workshop in March that we
114:55 

114:55 have and that conversation. So we're
114:57 

114:57 really trying to understand where you
114:58 

114:58 believe those biggest gaps are.
115:03 

115:03 So appreciate you continuing to take the
115:05 

115:05 survey and men team. We've got 204 of
115:08 

115:08 you in there. I'm hoping we can get to
115:09 

115:09 at least 100 survey responses again.
115:15 

115:15 >> Why don't we have all of the above?
115:18 

115:18 >> Yeah, everything. It's all a problem.
115:25 

115:25 So, so far it looks like the tools exist
115:27 

115:27 but are not aligned with the standards
115:28 

115:28 and the workflows. That seems consistent
115:30 

115:30 with what we've heard with you so far.
115:35 

115:35 Workforce capability lags strategy.
115:38 

115:38 That's a big one. Executive alignment is
115:40 

115:40 missing. We've heard that a few times
115:42 

115:42 now today.
115:44 

115:44 The tools exist. Workflows do not. We
115:46 

115:46 know that that's a a big reality as
115:47 

115:47 well.
115:55 

115:55 >> Thank you for continuing to weigh in.
115:56 

115:56 This is fun watching it in real time
115:58 

115:58 change.
116:06 

116:06 How many questions do we have left
116:08 

116:08 after?
116:08 

116:08 >> I think one or two. I think just one or
116:10 

116:10 two.
116:11 

116:11 >> Yeah, we're going a little over, but I
116:13 

116:13 think we're have a little
116:14 

116:14 >> or this actually might be the last
116:16 

116:16 question.
116:18 

116:18 >> We Well, it's okay. I think we're still
116:20 

116:20 okay, but
116:22 

116:22 >> Oh, no. We've got one more question. One
116:24 

116:24 more.
116:24 

116:24 >> We have We have some float, so we're
116:26 

116:26 we're
116:28 

116:28 >> All right. Well, this has been a really
116:29 

116:29 good conversation. And I love that the
116:30 

116:30 survey is being used to stimulate a
116:33 

116:33 discussion amongst the group. And so,
116:35 

116:35 you know, we encourage you to continue
116:36 

116:36 to weigh in both in the chat, but then
116:38 

116:38 raise your hand if you're a participant
116:40 

116:40 or a panelist. Um, and we'll unmute and
116:44 

116:44 have you share. That's the whole
116:46 

116:46 objective of what we're trying to do
116:47 

116:47 here is to get everybody to talk and
116:49 

116:49 communicate and collaborate.
116:53 

116:53 So, so far what I'm seeing is the tools
116:55 

116:55 exist but are not aligned with standards
116:56 

116:56 and workflows. That's overwhelmingly so
116:58 

116:58 far. uh the front runner but
117:03 

117:03 executive I mean yeah executive
117:04 

117:04 alignment workforce capability lags less
117:07 

117:07 so the data exists governance does not
117:18 

117:18 all right we'll give it another minute
117:19 

117:19 and then I'll move on to our last
117:21 

117:21 question
117:27 

117:27 >> yeah I think that um This result
117:30 

117:30 um does go a little bit to what I
117:33 

117:33 thought we heard before too is this
117:35 

117:35 idea. I mean we need standards, we need
117:37 

117:37 processes
117:39 

117:39 and we need the applications to
117:42 

117:42 adopt and utilize them. Um there's a lot
117:46 

117:46 of technology out there but
117:51 

117:51 does it do what we want?
118:02 

118:02 All right. So, I'm going to move on to
118:04 

118:04 our final question. It looks like the
118:06 

118:06 survey taking has slowed down. So, our
118:08 

118:08 final question is a word cloud. And so,
118:11 

118:11 one or two words only if you can. Where
118:13 

118:13 should DDSG focus to deliver the most
118:15 

118:15 value in the near future?
118:23 

118:23 We're trying to find a fast visual uh
118:26 

118:26 way
118:28 

118:28 um to make sure that we're aligned to
118:29 

118:29 the expectations and needs that this
118:31 

118:31 community has.
118:37 

118:37 Standards is a big one. I love it.
118:48 

118:48 Education, integration, those are two
118:50 

118:50 big ones. Communication
119:13 

119:13 So aligned workflows is another one that
119:16 

119:16 seems to be coming up quite a bit here.
119:19 

119:19 Processes and workflows and standards.
119:21 

119:21 That's big.
119:25 

119:25 The people, process, and technology. We
119:27 

119:27 can have the right technology, but
119:28 

119:28 without the people and the processes
119:29 

119:29 aligned, it becomes difficult to make
119:31 

119:31 progress in a meaningful way.
119:35 

119:35 Is there anything as this is coming
119:37 

119:37 through and we're finalizing this
119:39 

119:39 survey? Are there any pressing ideas or
119:42 

119:42 thoughts that the team wants to share?
119:43 

119:43 Please feel free to raise your hand here
119:44 

119:44 so we can unmute.
119:50 

119:50 Devon shared that a missing option was
119:51 

119:51 willingness to adopt but lack of
119:53 

119:53 understanding of how to transition to
119:55 

119:55 the wanted state. That's a very very
119:57 

119:57 good one, Devon. Thank you.
120:04 

120:04 Any other thoughts or comments from the
120:05 

120:05 team here today?
120:14 

120:14 >> I see a panelist. Hey Katie.
120:17 

120:17 >> Yeah. I just wanted to say I really
120:20 

120:20 appreciate this group because I feel
120:22 

120:22 like it brings more people into the
120:24 

120:24 conversation. I think that's just really
120:27 

120:27 really important. Even if your DOT
120:30 

120:30 hasn't started any kind of digital
120:33 

120:33 delivery initiative yet, just knowing
120:35 

120:35 what's out there is really important.
120:39 

120:39 So, thank you.
120:43 

120:43 >> Thank you so much, Katie. Any other
120:46 

120:46 thoughts or comments or feedback?
120:52 

120:52 All right. Well, I'll turn it back over
120:55 

120:55 to you, Matt and Roger.
121:05 

121:05 keep sharing.
121:13 

121:13 >> I think Roger, you're muted.
121:15 

121:15 >> Yeah, I was typing. Um, thanks thanks
121:18 

121:18 Mona. Um, and yeah, thanks everybody for
121:22 

121:22 your
121:24 

121:24 discussion there. Um and
121:28 

121:28 um a good I think like you said
121:31 

121:31 demonstration of what we want to try and
121:34 

121:34 do and collaborate. I see there do we
121:36 

121:36 did we figure this out? Do we have any
121:38 

121:38 issues with people, everyone that wants
121:41 

121:41 to um contribute, communicate, being
121:45 

121:45 able to
121:47 

121:47 um
121:54 

121:54 guess we got anybody that wanted to
121:57 

121:57 speak that didn't get a chance just
121:59 

121:59 given a last opportunity for that.
122:12 

122:12 Um, what do you think, Matt? Is there
122:15 

122:15 anything else we should I guess, you
122:17 

122:17 know, we got into this saying we had the
122:20 

122:20 meeting one, um, and we collected input
122:25 

122:25 there. We recorded what that is. Now,
122:28 

122:28 we've done another round of that with
122:30 

122:30 this meeting. We've obtained some great
122:33 

122:33 input which I think can be you know put
122:36 

122:36 into a number of different directions um
122:41 

122:41 um and uh between what's in the chat and
122:45 

122:45 what we've got dropped into the uh
122:49 

122:49 mural, we should really be able to get
122:53 

122:53 out of this that we can use going
122:56 

122:56 forward because I the idea here is we're
122:60 

122:60 we're trying to um use this input to
123:03 

123:03 guide where we're going. Um and yeah,
123:08 

123:08 this stuff we kind of we were we dropped
123:11 

123:11 in these survey questions here in the
123:14 

123:14 mural. So, if you want to continue to
123:17 

123:17 try to use the mural um and add anything
123:20 

123:20 to it, please feel free to do that.
123:23 

123:23 We'll keep using it and and working with
123:27 

123:27 it. Um,
123:29 

123:29 and uh I don't Yeah, I don't think
123:33 

123:33 there's anything else. Well, when we
123:36 

123:36 after we uh have our ASHTTO segment
123:38 

123:38 here, we're going to come back around
123:39 

123:39 and talk about the next meeting and
123:43 

123:43 where we're going. And so that some of
123:45 

123:45 these things, the idea would be to try
123:47 

123:47 to translate them into what we put into
123:49 

123:49 the agenda of our workshop and where do
123:52 

123:52 we need to focus and and dig in more
123:55 

123:55 deeply. So, I think we got some good
123:57 

123:57 input for that. Um, so maybe that's good
124:02 

124:02 for now and we'll um move on to the next
124:06 

124:06 section. Matt, anything else?
124:10 

124:10 Yeah, just um I think everybody you know
124:13 

124:13 to keep in mind again like as we move
124:16 

124:16 forward we want to take this information
124:19 

124:19 but be able to identify
124:22 

124:22 where the priorities are for us to try
124:25 

124:25 and you know bring our collective
124:27 

124:27 resources to address. So, if you've got
124:31 

124:31 suggestions, you know, in the mural
124:34 

124:34 about, you know, what are you really
124:35 

124:35 struggling with,
124:38 

124:38 um, you know, what's what's been a a big
124:40 

124:40 issue or hurdle for you or where is
124:42 

124:42 there a gap? I think those in particular
124:45 

124:45 will help us to kind of figure out the
124:48 

124:48 priorities and where we may need to
124:51 

124:51 strategize to try and find either
124:54 

124:54 additional resources to address or to um
124:60 

124:60 establish some sort of uh working groups
125:03 

125:03 or other targeted efforts uh as we move
125:07 

125:07 forward. Um,
125:10 

125:10 I think for us to be able to come back
125:12 

125:12 and, you know, have, hey, you know, this
125:16 

125:16 is a priority. This is keeping us from
125:18 

125:18 moving forward and being successful and
125:21 

125:21 be able to say, well, here's how you
125:23 

125:23 address it or develop a research needs
125:26 

125:26 statement perhaps is one option to to
125:29 

125:29 get funded to address that. Um, engage,
125:32 

125:32 you know, a technology vendor to
125:35 

125:35 address, you know, uh, why, etc. that
125:38 

125:38 that's going to be very helpful for us
125:40 

125:40 to so that way we're not not only are we
125:42 

125:42 capturing you know where kind of the
125:45 

125:45 current state of practice is but where
125:48 

125:48 we can be uh most targeted and
125:51 

125:51 beneficial in in contributing or having
125:54 

125:54 activities of of action.
126:00 

126:00 So, I just encourage everybody um
126:04 

126:04 you know to to
126:06 

126:06 >> okay
126:07 

126:07 >> provide those in the mural um and and we
126:10 

126:10 can then circle back to the DDSG and and
126:13 

126:13 have more targeted conversations
126:16 

126:16 uh in targeted activities.
126:22 

126:22 >> Okay. Well then um um I guess we will
126:27 

126:27 move on. Um but yeah, keep that all in
126:30 

126:30 mind everybody. We're And um Devin, is
126:34 

126:34 your hand raised a recent one or
126:37 

126:37 >> Yeah, I got a Yeah, I have a quick
126:39 

126:39 question before um going into the the
126:42 

126:42 next part of this. Uh I'm trying to do
126:44 

126:44 my due diligence and look through some
126:46 

126:46 of the stuff on the mural board and I
126:47 

126:47 wanted to just confirm something on the
126:50 

126:50 schedule here, the DDSG schedule. these
126:54 

126:54 dates that are targeted for the future.
126:56 

126:56 I know the next three they're the
126:58 

126:58 virtual ones. All of those other
127:00 

127:00 meetings that are listed, are those
127:02 

127:02 proposed times to combine this meeting
127:06 

127:06 into that week or is that just an
127:09 

127:09 awareness of all the other activities
127:12 

127:12 that are happening?
127:14 

127:14 I guess you could call it
127:17 

127:17 >> the the ladder Devon if you're if you're
127:20 

127:20 talking about this particular what what
127:22 

127:22 Roger's showing
127:23 

127:23 >> right
127:23 

127:23 >> that this is for us to be a help
127:26 

127:26 identify where we have opportunities to
127:29 

127:29 either collaborate and colllocate and or
127:32 

127:32 avoid so that we're not in conflict
127:35 

127:35 because it's going to take you know
127:37 

127:37 either members or others away from being
127:40 

127:40 able to actively participate with us.
127:42 

127:42 So,
127:43 

127:43 >> okay.
127:43 

127:43 >> But we'll we will be discussing towards
127:45 

127:45 the end of today as part of the wrap-up
127:47 

127:47 kind of like the the future uh
127:50 

127:50 scheduling and and priorities and where
127:52 

127:52 we want to target.
127:54 

127:54 >> Okay. Thank you.
127:55 

127:55 >> Yeah.
127:59 

127:59 All right. Well, then I think um
128:03 

128:03 Trisha, are you here? Um good. See you.
128:09 

128:09 Thanks. Um, and I think maybe Jennifer
128:13 

128:13 wasn't able to join today. So, um, maybe
128:19 

128:19 um, we'll start with Trisha, you going
128:22 

128:22 over what Jstan is up to, what are the
128:25 

128:25 new things, and maybe give people a
128:26 

128:26 little perspective on Jstand that may
128:29 

128:29 not be as aware as others. And then um
128:35 

128:35 if I don't know if anybody wants to if
128:37 

128:37 anybody that's on um uh JTCE will or
128:43 

128:43 Allen um wants to just say a few words
128:46 

128:46 about what you're focused on after
128:48 

128:48 Trisha um shares her presentation and
128:52 

128:52 then I think this is really kind
128:54 

128:54 offormational mostly for us to keep
128:56 

128:56 everybody informed and also if there are
129:00 

129:00 any things the DD ESG should do. We
129:03 

129:03 would we would talk about that.
129:09 

129:09 Does that sound good? Uh Matt, maybe I
129:12 

129:12 jumped in there, but I was trying to
129:14 

129:14 Yeah. See if we're ready to go on to
129:16 

129:16 this.
129:17 

129:17 >> Yeah. Yeah, that's that's perfect.
129:22 

129:22 >> Okay. Uh
129:28 

129:28 let's see. how to make this a
129:30 

129:30 presentation.
129:35 

129:35 >> I will maybe Rackley if you're on um
129:38 

129:38 there's been a couple questions in the
129:41 

129:41 the chat just about when we think the
129:44 

129:44 recordings will be available. Um perhaps
129:48 

129:48 you can just verbally
129:51 

129:51 >> Right. So after this meeting concludes
129:54 

129:54 um it'll take a couple maybe an hour
129:56 

129:56 maybe two hours for this to get
129:58 

129:58 processed and then we have to find a way
129:60 

129:60 to
130:01 

130:01 uh
130:03 

130:03 uh clip it appropriately and put closed
130:06 

130:06 captions on it and then we have to post
130:08 

130:08 it on our website um which we're
130:11 

130:11 currently working on for the previous I
130:13 

130:13 Heat meeting recording um that should be
130:16 

130:16 done any day now. this once we've done
130:18 

130:18 that uh for the first meeting, it should
130:20 

130:20 be very easy for us to do this one. So,
130:22 

130:22 uh very very shortly is is my is my
130:25 

130:25 answer. Um yeah, it'll be available in
130:29 

130:29 full closed captions. Um a transcript
130:32 

130:32 will be available, all those things. Of
130:34 

130:34 course, the mural will continue to be
130:36 

130:36 available for all time.
130:40 

130:40 >> Thanks, Rackley. and and perhaps not,
130:43 

130:43 you know, not before our next meeting on
130:45 

130:45 Monday, particularly maybe with the
130:47 

130:47 impending weather events that that may
130:50 

130:50 impact a lot of people, uh, including
130:52 

130:52 NIB staff. So,
130:54 

130:54 >> correct. I may have no power very
130:56 

130:56 shortly.
130:58 

130:58 >> Y,
130:59 

130:59 >> thanks for
131:02 

131:02 >> Let's hear from Jstand before that
131:04 

131:04 happens then.
131:07 

131:07 Roger, I have to point out you guys, it
131:09 

131:09 says the only thing missing is the
131:10 

131:10 yellow brick road. That was my note
131:13 

131:13 right there. Right. So, I just had to
131:16 

131:16 point that out. That was for a different
131:17 

131:17 presentation, but I think it's funny
131:19 

131:19 because we just are missing the yellow
131:21 

131:21 brick road for all this because that's
131:22 

131:22 how it's going to end.
131:23 

131:23 >> Yeah.
131:25 

131:25 Darn.
131:28 

131:28 >> Forever an optimist.
131:31 

131:31 >> Well, we can always keep looking for it.
131:34 

131:34 So, I put in the chat, you guys, the um
131:37 

131:37 link to Jstand. So, I think that is
131:40 

131:40 there. I also tried to put it on the
131:42 

131:42 mural board. Um it's really small. I
131:46 

131:46 find the mirror board to be awesome.
131:48 

131:48 It's just that it um takes, you know,
131:51 

131:51 every bit of my technology like
131:53 

131:53 savviness sometimes. So, uh I don't know
131:57 

131:57 how to increase the font on my sticky
131:59 

131:59 note, but but thank you, Roger. Are you
132:03 

132:03 guys ready for me to start?
132:05 

132:05 >> Yeah, sure, Trisha.
132:06 

132:06 >> All right. Awesome. Really glad to be
132:09 

132:09 here today and be part of this group.
132:11 

132:11 Um, if you would have asked me two years
132:13 

132:13 ago if I would be sitting in a digital
132:16 

132:16 delivery stakeholder group, I would have
132:17 

132:17 said no way. Um, and so I am just
132:21 

132:21 thrilled to be here. My background is in
132:24 

132:24 asset management. uh and I do have
132:27 

132:27 slides that I present to say please
132:29 

132:29 asset management people get in the room
132:33 

132:33 with your design and construction folks
132:36 

132:36 and tell them what you want. Um so it's
132:38 

132:38 really been quite a journey for me to
132:41 

132:41 add what I feel like is my expertise
132:44 

132:44 area to some of the areas that I may not
132:47 

132:47 know as well um and that I might not
132:50 

132:50 chime in. So again, uh, thank you for
132:52 

132:52 having me today and and allowing me to
132:54 

132:54 be in this group. I want to give an
132:57 

132:57 update and put on my ASHTO subcommittee
132:60 

132:60 on data standardization hat today and
133:03 

133:03 talk about JSAN. I did talk about this
133:05 

133:05 at our first meeting, but it's good
133:07 

133:07 again to just say who we are, uh, what
133:10 

133:10 we're trying to do and then give you
133:12 

133:12 some updates. Uh so we were put together
133:15 

133:15 actually in October 2019
133:19 

133:19 um AR1-9
133:21 

133:21 I'll never forget that number probably
133:23 

133:23 for my whole life but that this internal
133:26 

133:26 cross committee multidiscipline group
133:28 

133:28 within ASHTDO should be formed and we
133:31 

133:31 were really formed these are some words
133:33 

133:33 that we maybe don't always use with
133:35 

133:35 executives but we want to coordinate
133:37 

133:37 standards schemas look at where the gaps
133:41 

133:41 are kind of across ASHTTO with data
133:43 

133:43 standards resolve conflicts. You know,
133:46 

133:46 there's several sets of data standards
133:48 

133:48 that could exist within the maintenance
133:50 

133:50 community as well as the asset
133:52 

133:52 management community construction. And
133:54 

133:54 so, we want to look at those gaps,
133:56 

133:56 resolve any conflicts, and avoid
133:58 

133:58 duplication of efforts um across these
134:00 

134:00 committees. So you can see this we're
134:02 

134:02 made up of the council and highways and
134:04 

134:04 streets which is policy
134:07 

134:07 program delivery and operations bridges
134:09 

134:09 and structures construction
134:11 

134:11 transportation system operations which
134:13 

134:13 was added uh to our committee design
134:16 

134:16 data and analytics performance-based
134:18 

134:18 management and then the special
134:20 

134:20 committee on ashaware and we are
134:22 

134:22 underneath data and analytics. So, we
134:25 

134:25 are a subcommittee um and we cannot we
134:27 

134:27 do not have voting authority. We do not
134:29 

134:29 have funding. Um but we've been pushing
134:31 

134:31 to say that this is very important and
134:34 

134:34 establishing this group. Uh and seeing
134:36 

134:36 the word standards, I mean, I want to
134:38 

134:38 take a picture and just put that like on
134:41 

134:41 my computer that everybody cares about
134:43 

134:43 standards that Jan is doing the right
134:46 

134:46 thing uh wanting to to move this
134:48 

134:48 forward. Thank you. Next slide.
134:53 

134:53 So what is our mission? This was
134:55 

134:55 established I think years ago uh with a
134:58 

134:58 chair before me. We have revisited this
134:60 

134:60 mission to say we are going to champion
135:02 

135:02 and coordinate efficient information
135:04 

135:04 flow throughout the life cycle of all
135:06 

135:06 assets related information that comprise
135:09 

135:09 of our transportation systems. We're
135:11 

135:11 going to do this through open data
135:13 

135:13 standards, data governance, that schema
135:15 

135:15 word again, development and
135:17 

135:17 collaborative public and private
135:19 

135:19 partnerships. Thank you, Roger. Next
135:21 

135:21 slide.
135:23 

135:23 So, this is our membership. I'm really
135:25 

135:25 looking to fill vacancies. I have been
135:27 

135:27 for a while. We do not It's probably
135:30 

135:30 going to be a question in the chat.
135:31 

135:31 Right now, we don't have friends invited
135:33 

135:33 to our meetings because we've been
135:35 

135:35 trying to establish kind of where we are
135:38 

135:38 so that again we can try to get some
135:40 

135:40 voting authority, get funding, figure
135:42 

135:42 out how is ASHTTO going to adopt modern
135:46 

135:46 digital data standards. And so we've
135:48 

135:48 been trying to work on all those things.
135:50 

135:50 We have people that are interested in
135:52 

135:52 these vacancies, but I want to point out
135:54 

135:54 to you the people that are part of the
135:55 

135:55 committee. We've had people leave that
135:57 

135:57 have done amazing work. Uh these folks
135:60 

136:00 contribute a lot of their time to really
136:03 

136:03 talking about it to really promoting
136:05 

136:05 standards. I want to especially say
136:07 

136:07 thank you to Will Holmes. I could not do
136:09 

136:09 this without him. You've heard him today
136:11 

136:11 already. Um he's amazing. And so many
136:14 

136:14 other people. everyone I would consider
136:16 

136:16 to be just awesome partners and friends.
136:18 

136:18 So, thank you. Next slide, Roger.
136:24 

136:24 So, then what are modern transportation
136:26 

136:26 data standards? Just so that we're all
136:28 

136:28 kind of aware um on this. So, agreed
136:30 

136:30 upon rules for how transportation
136:32 

136:32 related data is formatted, shared,
136:35 

136:35 interpreted. I find that when I talk
136:37 

136:37 about these modern data standards, you
136:39 

136:39 know, we're not talking about books.
136:41 

136:41 We're not talking about we can say
136:43 

136:43 colors green book blue book. We're
136:44 

136:44 talking about now a common language that
136:47 

136:47 allows technologies like traffic,
136:49 

136:49 signals, buses, you know, apps to
136:52 

136:52 understand each other and work together.
136:55 

136:55 So those are modern transportation data
136:57 

136:57 standards.
136:59 

136:59 Next slide. Roger. I like it that you
137:01 

137:01 can move the slides.
137:04 

137:04 I never have it. I always say I need
137:06 

137:06 like a personal driver. I need a
137:08 

137:08 personal assistant. Thank you, Roger. So
137:11 

137:11 what happened was I think I've been
137:13 

137:13 doing this for a couple years and and
137:15 

137:15 talking about again Jan doesn't have the
137:17 

137:17 right to do um you know voting authority
137:19 

137:19 and adopt and how is ASHTO going to go
137:22 

137:22 about this. So in the 2025 ASHTO annual
137:25 

137:25 meeting in Salt Lake City this was
137:28 

137:28 brought up JSAN was brought up at two
137:30 

137:30 different meetings. So the council on
137:32 

137:32 highways and streets which is mostly
137:34 

137:34 kind of engineeringesque folks at high
137:36 

137:36 levels across the agency and there was a
137:39 

137:39 presentation thank you to UD do for
137:41 

137:41 doing that presentation and to talking
137:43 

137:43 about the urgency the need for this as
137:47 

137:47 well as the strategic management
137:48 

137:48 committee. Um those are ASHTTO elected
137:51 

137:51 leadership and chairs of those modal
137:53 

137:53 councils. So great group. They decide
137:56 

137:56 more about policy. They discussed some
137:58 

137:58 of our accomplishments, some things that
137:60 

137:60 we've done, the poolled funds, um
138:02 

138:02 probably this group, and then the
138:04 

138:04 collaborative work of the ASHTO
138:05 

138:05 committees, BIM and digital delivery.
138:07 

138:07 So, those conversations were had. I
138:09 

138:09 wished I could have been, you know, in
138:11 

138:11 those meetings, but it was exciting to
138:13 

138:13 hear, okay, is something going to
138:15 

138:15 change? Next slide.
138:19 

138:19 So, something changed. The light bulb
138:21 

138:21 came on and they said, we need to do
138:24 

138:24 something. And so it's exciting to
138:26 

138:26 announce that this ASHTTO task force on
138:28 

138:28 data standards I specifically wrote
138:30 

138:30 exactly what was sent to me in the email
138:33 

138:33 because this can be confusing
138:35 

138:35 terminology can be confusing. So this is
138:38 

138:38 called the ASHTSTO task force on data
138:40 

138:40 standards for digital delivery and asset
138:43 

138:43 management and it was established it was
138:45 

138:45 established by the strategic management
138:47 

138:47 committee. It's going to be chaired by a
138:49 

138:49 member of the ASHTOA board of directors
138:52 

138:52 and then the ASHTO force will include
138:54 

138:54 the following chairs or their design. So
138:56 

138:56 you can see those one, two, three, four,
138:58 

138:58 five, six, seven, eight, nine folks
139:01 

139:01 including the the director. Um, and I
139:04 

139:04 get to be in on these meetings really
139:07 

139:07 excited to kind of speak for the nation
139:09 

139:09 for Jan as well as I can on how we need
139:12 

139:12 to move forward with national standards.
139:15 

139:15 Next slide.
139:20 

139:20 And so um the words exactly again
139:24 

139:24 because we have not met yet. So we're
139:27 

139:27 looking to meet hopefully in the next
139:28 

139:28 four weeks and I'm kind of preparing for
139:31 

139:31 that meeting thinking about what they
139:33 

139:33 need to know um all the work that we've
139:35 

139:35 been doing. But this new
139:36 

139:36 multid-disciplinary task force will
139:38 

139:38 review the importance and impact of
139:41 

139:41 digital delivery on state DOS and they
139:43 

139:43 will develop recommendations on
139:46 

139:46 opportunities to enhance and improve
139:48 

139:48 integration of BIM and digital delivery
139:50 

139:50 across ASHTO structure. So how do we do
139:52 

139:52 this? How do we create maintain and
139:56 

139:56 publish these digital standards? um this
139:58 

139:58 group is going to kind of figure out
140:01 

140:01 what is the again what is the
140:03 

140:03 recommendation on how to do this with
140:05 

140:05 the current ASHTO structure does not
140:07 

140:07 publish digital standards at this point
140:10 

140:10 they just publish books they have a way
140:12 

140:12 to do that um so we're looking at that
140:14 

140:14 structure and that process and then
140:17 

140:17 reporting back um to the strategic
140:19 

140:19 management committee at the spring
140:21 

140:21 meeting so we have to do a report in at
140:23 

140:23 six months that means we have to get
140:25 

140:25 something done I appreciate that right
140:27 

140:27 And then we need to make recommendations
140:30 

140:30 um at that the board of directors and
140:32 

140:32 the 2026 ASHTO annual meeting. Um so
140:35 

140:35 where does Janet fit into this? I could
140:37 

140:37 have made another slide. Um Jan is going
140:39 

140:39 to support this. JSAN is going to be
140:42 

140:42 there if there's questions. We're going
140:43 

140:43 to get go back to our parent committees.
140:46 

140:46 Um we're going to you know facilitate
140:48 

140:48 and and have conversations and JSAN is
140:51 

140:51 going to stay where it is uh in full
140:53 

140:53 capacity. We will have meetings every
140:54 

140:54 month just like we have been because you
140:57 

140:57 know that times goes quickly as you are
140:59 

140:59 aware right you have three hours four
141:01 

141:01 hours today and it can go very fast and
141:04 

141:04 so we need JSAN to help support this
141:06 

141:06 ASHTO task force
141:09 

141:09 so that was it I think Roger that's my
141:11 

141:11 update I'm pretty excited um because I
141:15 

141:15 feel like we have movement so I would
141:17 

141:17 just make a request of all of you to
141:19 

141:19 continue to reinforce the fact that we
141:22 

141:22 need digital modern standards and that
141:25 

141:25 that needs to come through ASHTO. Um
141:27 

141:27 they need to be adopted through ASHTO.
141:30 

141:30 If we have that national adoption, I've
141:32 

141:32 talked to you know Texas, CALR, we're
141:34 

141:34 all such good friends saying we need
141:36 

141:36 this um how can we get this so that then
141:39 

141:39 we can all you know bring that back to
141:41 

141:41 our state and start to work towards
141:43 

141:43 again these these standards across the
141:45 

141:45 industry.
141:47 

141:47 >> So I think that's it. Yes. Any questions
141:50 

141:50 or
141:52 

141:52 >> Yeah.
141:52 

141:52 >> Yeah. There might be some questions but
141:55 

141:55 um well I have one um if I
141:58 

141:58 >> man well um so I I guess this effort
142:03 

142:03 this strategic management committee
142:05 

142:05 effort is really taking what Jstan was
142:09 

142:09 going to be doing and elevating it to be
142:12 

142:12 across the whole of ASHTO at the highest
142:17 

142:17 level um versus being operating under
142:20 

142:20 like you showed us initially under the
142:22 

142:22 other committees and uh giving it more
142:26 

142:26 strength focus. Um
142:30 

142:30 >> yeah, and I see Kevin has
142:33 

142:33 >> Kevin's on today too. That's awesome. So
142:35 

142:35 Kevin can chime in. But this task force
142:38 

142:38 isn't to take on to do any J stands
142:40 

142:40 still exists and J stands still there as
142:42 

142:42 a subcommittee. This task force is a
142:44 

142:44 special task force that was created just
142:46 

142:46 for a temporary amount of time to kind
142:48 

142:48 of determine the direction and it is
142:51 

142:51 made up of like executive level folks or
142:53 

142:53 their designates. So that's good. So
142:55 

142:55 higher level decision makers you know
142:57 

142:57 that understand across ASHTO I would say
142:59 

142:59 the organization the policies that can
143:02 

143:02 help to guide sort of what what should
143:04 

143:04 we do within the the structure and Kevin
143:07 

143:07 please feel free to jump in.
143:10 

143:10 >> Sure. Thanks uh Trisha. Um, I think I
143:13 

143:13 would just add kind of from the the ASCO
143:15 

143:15 staff perspective, great presentation,
143:17 

143:17 SA, thank you for that. The and SA
143:20 

143:20 really hit on this. The idea is of this
143:23 

143:23 task force is it it was likely sunset
143:26 

143:26 within a year, bring folks together and
143:28 

143:28 and really look at I'll say more the
143:30 

143:30 organizational model associated with
143:32 

143:32 this where JAN has is and will continue
143:35 

143:35 to work and plays a really important
143:37 

143:37 role. But how does that fit within all
143:39 

143:39 of our committees? because data is
143:41 

143:41 interrogate, you know, is integral to
143:42 

143:42 everything that we're doing, you know,
143:44 

143:44 our members are doing the DOTS and
143:46 

143:46 within the ASCO committee. So, it's it's
143:48 

143:48 to look at that. It's also to look at
143:50 

143:50 things like, okay, if we do have
143:52 

143:52 initiatives as we move forward, what
143:54 

143:54 what is how how do we support those
143:56 

143:56 financially and with the kind of the
143:58 

143:58 human resources side of things as well.
144:01 

144:01 So, it it's kind of a little bit more o
144:04 

144:04 overarching, if you will. I I tend to
144:05 

144:05 think of it as, you know, it's not a
144:08 

144:08 perfect analogy, but you know, at some
144:10 

144:10 point 50 years ago, somebody said,
144:11 

144:11 "Okay, how are we going to look at
144:13 

144:13 research?" Because everybody's doing
144:14 

144:14 research. How do we do that within
144:15 

144:15 Asheville? And we came together and
144:17 

144:17 figured that out. So this is this is
144:20 

144:20 might not be a perfect example, but
144:22 

144:22 we're we're really trying to make sure
144:23 

144:23 that we have the structure in place to
144:25 

144:25 support the importance of the work
144:26 

144:26 that's going on here and and also really
144:29 

144:29 how to how to define what is Asheville's
144:31 

144:31 role in this because we we have you know
144:34 

144:34 in listening to the conversation earlier
144:36 

144:36 Ashville has a role to a point and then
144:38 

144:38 it's it's to our members and and others
144:41 

144:41 as well on how to do it from the
144:42 

144:42 organizational side of things and then
144:44 

144:44 Trisha mentioned it as well. It's also
144:46 

144:46 to look at what are the models out there
144:48 

144:48 for how we publish digital standards
144:50 

144:50 because that's not something that uh we
144:53 

144:53 typically do at a show. So, uh hopefully
144:55 

144:55 that helps and and supplemented the the
144:59 

144:59 great uh the great presentation that
145:00 

145:00 Trisha just gave.
145:07 

145:07 >> Yeah, thanks Kevin.
145:10 

145:10 And by the way, Kevin is one of the
145:13 

145:13 members of the one of the DDSG members
145:16 

145:16 um who I think we didn't get to
145:18 

145:18 introduce uh initially, but he's here
145:21 

145:21 now. So that's great.
145:24 

145:24 >> Yeah, thanks for joining Kevin. Uh
145:26 

145:26 Trisha question I guess followup is like
145:30 

145:30 do you expect moving forward that
145:33 

145:33 there's
145:35 

145:35 something out of Jstand that would need
145:38 

145:38 our attention as a DDSG or that you
145:42 

145:42 would prefer that we you know contribute
145:44 

145:44 or comment on?
145:48 

145:48 >> Yeah that's a good question Matt. I
145:49 

145:49 think we'll have to kind of take it one
145:51 

145:51 step at a time, but having this group
145:53 

145:53 available is is awesome. Um, I think
145:57 

145:57 what was missing maybe uh is the
145:59 

145:59 industry partners, you know, and others
146:01 

146:01 and having just open dialogue. So, I'm
146:04 

146:04 sure I I'm, you know, I'm I'm willing to
146:07 

146:07 give updates and we can kind of take
146:10 

146:10 this as it goes with the task force and
146:12 

146:12 see where we are. Um, how long is our
146:16 

146:16 group going to meet? I don't think
146:18 

146:18 there's an end date to this right now,
146:20 

146:20 right? The digital delivery stakeholder
146:23 

146:23 group.
146:23 

146:23 >> No. No, there's not.
146:25 

146:25 >> Yeah. Okay. So, I think there'll be lots
146:28 

146:28 of opportunity for collaboration.
146:32 

146:32 >> Okay. Excellent.
146:41 

146:41 >> Roger. I know. Um so we don't have
146:47 

146:47 um Jennifer Lloyd available.
146:51 

146:51 She like Trisha is leading uh ASHTO
146:55 

146:55 efforts on the JTCE. I think we do have
146:59 

146:59 a few other uh members that are involved
147:03 

147:03 with JTCE.
147:07 

147:07 Um, not that I want to put them on the
147:09 

147:09 spot, but I'm going to uh if if anybody
147:14 

147:14 might want to just maybe briefly give
147:16 

147:16 maybe a couple items that maybe they're
147:18 

147:18 aware of or
147:21 

147:21 um might be of interest to the group or
147:25 

147:25 >> I can do that, Matt.
147:26 

147:26 >> Perfect. Thank you.
147:28 

147:28 >> Sure. Uh so right now uh again JTCE is
147:34 

147:34 uh still finding their uh feet after uh
147:38 

147:38 um recent departure uh with our chair.
147:42 

147:42 So now Jennifer Lloyd is now the uh
147:44 

147:44 chair and uh Sam uh Woods from Georgia
147:48 

147:48 DOT is the uh is the co-chair. Uh two of
147:53 

147:53 the items that uh we are currently
147:56 

147:56 focused on. one is updating the digital
147:60 

147:60 delivery I guess guidance document uh
148:03 

148:03 that uh JTC EEes put out a couple years
148:06 

148:06 ago. Uh and the other large item that uh
148:11 

148:11 we are currently undertaking is the uh
148:16 

148:16 model viewer requirements. So what is
148:20 

148:20 required in a model viewer? Um so we are
148:26 

148:26 working with uh you know we've held
148:29 

148:29 multiple workshops
148:31 

148:31 um from the past probably six uh months
148:34 

148:34 or so. So with uh Ashtto committee on
148:37 

148:37 design, committee on construction, there
148:40 

148:40 was a workshop held at uh IHEA. Um so
148:44 

148:44 there was a recent workshop held at uh
148:47 

148:47 TRB and we'll also have an additional
148:50 

148:50 workshop to collect the input from our
148:54 

148:54 contracting community as well. So this
148:57 

148:57 is uh nonprouctspecific
149:01 

149:01 uh model view requirements. So really
149:04 

149:04 it's laying out for software vendors of
149:08 

149:08 what um certain personas will need in a
149:13 

149:13 model viewer. So if you're a project
149:15 

149:15 manager, what uh you know functions and
149:19 

149:19 functionality are you going to need to
149:21 

149:21 cover that persona? Uh there will be a
149:24 

149:24 lot of overlap from multiple different
149:27 

149:27 uh areas, but it really breaks that
149:29 

149:29 down. Then it helps the DOS per se in a
149:33 

149:33 way that you know as you're developing
149:35 

149:35 training on what are those items that
149:38 

149:38 you're going to need to teach to a
149:40 

149:40 project manager or a you know an
149:43 

149:43 inspector in construction and so forth.
149:46 

149:46 So looking at it holistically on uh that
149:50 

149:50 model viewer not just on the design side
149:53 

149:53 or just on the construction side uh
149:56 

149:56 because as we're moving these digital
149:57 

149:57 models through you're you know you have
150:00 

150:00 you know traffic control technicians you
150:02 

150:02 have utilities you have all of these
150:05 

150:05 different uh folks that are touching a
150:08 

150:08 model viewer. What information do they
150:11 

150:11 actually need out of a model viewer? not
150:13 

150:13 only helping the software industry help
150:15 

150:15 develop you know products that meet our
150:18 

150:18 our needs uh because right now there is
150:21 

150:21 nothing stating of what everybody really
150:23 

150:23 needs. So instead of having a DOT say I
150:27 

150:27 need you know functionality A B and C
150:29 

150:29 and another one saying I need 1 2 3
150:32 

150:32 we're coming together with a
150:33 

150:33 collaborative uh you know voice of
150:37 

150:37 saying this is what we need uh as the
150:41 

150:41 industry to cover this group of uh of
150:44 

150:44 users. So that is one of the big efforts
150:46 

150:46 that we are uh undertaking uh with JTC
150:50 

150:50 EAS currently.
150:55 

150:55 Thank you, Alan. Appreciate
151:02 

151:02 >> it seems like you had a pretty good
151:03 

151:03 attendance at the TRB event as well.
151:09 

151:09 >> Yes. Yes. I I think there was great
151:11 

151:11 attendance. Uh again, they've been very
151:13 

151:13 interactive workshops uh to get uh this
151:17 

151:17 information out. what are those
151:19 

151:19 priorities that our you know the
151:21 

151:21 industry is finding so and a wide swath
151:24 

151:24 of uh wide swath of users
151:29 

151:29 >> um Allan have um I guess there are a
151:32 

151:32 number of model viewers out in the
151:35 

151:35 market um do you use those as a starting
151:38 

151:38 point or have you just basically gone
151:40 

151:40 back to process and requirements um
151:44 

151:44 >> yeah so I mean it's it's really looking
151:46 

151:46 at the functionality So if you know it
151:49 

151:49 might be identifying an alignment or
151:52 

151:52 what I mean so it's down to the basic
151:54 

151:54 functionality of what you need as you
151:58 

151:58 know to view the model.
152:00 

152:00 >> Uh so you know and it's really looking
152:02 

152:02 at what what is a model viewer and what
152:04 

152:04 is not. So it's not going to edit it.
152:07 

152:07 It's not going to schedule it. It you
152:09 

152:09 know there's all of these different
152:10 

152:10 programs that ultimately
152:13 

152:13 have those different features that you
152:15 

152:15 know we'll pull into this. But this is
152:17 

152:17 ultimately looking at how do we view the
152:19 

152:19 model? What are those requirements to
152:22 

152:22 view the model? Is it you know the you
152:24 

152:24 know that linear reference system to be
152:26 

152:26 able to see where you are on you know on
152:28 

152:28 a project and and so forth. So some of
152:31 

152:31 those basic functionalities are going to
152:33 

152:33 be crosscutting on every you know uh
152:36 

152:36 persona that you're getting into but you
152:38 

152:38 know there are different functionalities
152:40 

152:40 that you know you know this one might
152:42 

152:42 need this specific task. Uh so it's
152:45 

152:45 really trying to lay that out. Uh so
152:47 

152:47 it's not really looking at any one
152:49 

152:49 vendor's uh product to say here they can
152:53 

152:53 do it because we all know uh there's not
152:56 

152:56 one platform that does everything that
152:58 

152:58 we need. Uh so really trying to lay out
153:02 

153:02 what are those requirements for each of
153:05 

153:05 the personas that are going to be
153:08 

153:08 utilizing a model viewer and how do we
153:10 

153:10 view it and interact with that model.
153:15 

153:15 And as I recall, there were quite a lot
153:17 

153:17 of personas.
153:19 

153:19 >> Uh yes,
153:21 

153:21 very much so. I don't remember off the
153:23 

153:23 top of my head, but there are yes, it's
153:26 

153:26 well over uhund and some different
153:28 

153:28 personas that, you know, we're looking
153:30 

153:30 at.
153:31 

153:31 >> So, I mean, this this this matrix is is
153:34 

153:34 going to be very large.
153:35 

153:35 >> Uh so, you know, really laying that out.
153:39 

153:39 um you know cuz there are so many
153:41 

153:41 different people and uh roles that are
153:45 

153:45 going to touch a model. I mean you
153:46 

153:46 figure it's your complete life cycle of
153:48 

153:48 a project uh to be able to interact with
153:51 

153:51 these models. So you know it might be
153:52 

153:52 asset management, it might be you know
153:55 

153:55 planning or or whatever but how do you
153:57 

153:57 view a model or view that model
153:59 

153:59 information?
154:01 

154:01 >> Yeah. And even even you know like
154:04 

154:04 fabricators and others as well.
154:07 

154:07 >> Yep. Yeah. This is not just internal to
154:10 

154:10 do you know you're looking at you know
154:12 

154:12 the construction uh folks as well. So
154:15 

154:15 you have biders you have foremen you
154:17 

154:17 have laborers you you know what do they
154:20 

154:20 need uh in this and fabricators
154:23 

154:23 suppliers and so forth. How do they view
154:25 

154:25 it? How do they get to that information?
154:26 

154:26 What information do they need out of a
154:28 

154:28 model?
154:31 

154:31 >> Yeah.
154:33 

154:33 Excellent. And I'm sure we'll have an
154:35 

154:35 opportunity to have you maybe uh go into
154:38 

154:38 more detail with the group moving
154:40 

154:40 forward.
154:42 

154:42 >> But uh yeah, thanks Alan for stepping up
154:44 

154:44 and and adding that information.
154:47 

154:47 >> Sure thing.
154:57 

154:57 >> Rogers taking some notes, I see.
155:00 

155:00 >> Yeah. um just took a few notes on what
155:04 

155:04 we heard from the ASHTO committees and I
155:07 

155:07 guess that you might ask the same
155:09 

155:09 question of Allen or if or it could be a
155:13 

155:13 future question. Maybe we'll we'll put a
155:16 

155:16 this a little bit more on the agenda for
155:18 

155:18 the next meeting to see what does what
155:21 

155:21 might this committee need from the DDSG
155:23 

155:23 in terms of sounds like they're pretty
155:26 

155:26 engaged with a lot of different
155:27 

155:27 stakeholders. So, from that standpoint,
155:30 

155:30 they seem to be getting input, but maybe
155:33 

155:33 there's a way there might be things we
155:36 

155:36 could help with with the DDSG.
155:39 

155:39 Um
155:42 

155:42 >> yeah, I mean I don't want to put Allan
155:44 

155:44 on the spot to speak on behalf of the
155:47 

155:47 committee, but I I think you know he can
155:49 

155:49 certainly carry the message, you know,
155:51 

155:51 back to the group that if there's a role
155:53 

155:53 that they feel like uh we can help or or
155:56 

155:56 contribute to, we certainly would be
155:59 

155:59 open to to that communication and
156:01 

156:01 dialogue.
156:02 

156:02 >> Yep. I will carry that back.
156:08 

156:08 >> And uh yeah, I see Trisha has to step
156:11 

156:11 away. Thanks, Trisha. Appreciate your
156:14 

156:14 engagement as always. Trisha's very
156:16 

156:16 busy. I don't know how she does it. She
156:18 

156:18 takes on a lot of uh great efforts and
156:21 

156:21 activities and um has been a big
156:24 

156:24 champion in the space for some time.
156:29 

156:29 And uh uh like like pretty much
156:31 

156:31 everybody on on the DDSG, it's not meant
156:34 

156:34 to say that nobody's engaged. I hope
156:37 

156:37 that didn't come across that way. Um,
156:41 

156:41 people like Allan and and uh Devin and
156:45 

156:45 Katie and
156:47 

156:47 Will and and everybody have have been
156:49 

156:49 big champions in in this space for some
156:52 

156:52 time and we're always looking for them
156:54 

156:54 to help guide us and provide
156:56 

156:56 information.
157:01 

157:01 Um, Rogers, that's a good point. We got
157:05 

157:05 uh we got about 20 minutes. Maybe we
157:07 

157:07 want to pivot to I will I see your hand.
157:10 

157:10 Go ahead, Will.
157:11 

157:11 >> Yeah. Um well, there was Nathan had put
157:14 

157:14 something in the chat and I just wanted
157:16 

157:16 to respond to it uh quickly. Um as far
157:21 

157:21 as development of IFC and ISO, um that
157:26 

157:26 is ongoing and active and continuing. So
157:29 

157:29 IFC is not a static uh thing. IFC 43 is
157:34 

157:34 out right now. Uh there is work to make
157:37 

157:37 IFC 44 which will include tunnels and
157:40 

157:40 some other things. Uh and that will go
157:43 

157:43 forward into the ISO standard. Um I uh
157:48 

157:48 IFC 5 is is an ongoing effort that will
157:53 

157:53 um move from strictly file-based to more
157:56 

157:56 of a serviceoriented architecture. that
157:59 

157:59 that will not be emerging immediately
158:02 

158:02 but that is that is very clearly on the
158:05 

158:05 horizon and a need that the clearly uh
158:08 

158:08 not only the DOS but everybody needs um
158:12 

158:12 to be able to handle things in a more
158:14 

158:14 efficient way. So just wanted to let
158:17 

158:17 y'all know that's uh work that Trisha
158:20 

158:20 does at the national level and then I'm
158:22 

158:22 working on the infrastructure
158:24 

158:24 infrastructure domain steering
158:26 

158:26 committee. Um we are trying to bring US
158:31 

158:31 interests to that. There is an effort uh
158:35 

158:35 starting to kick off should be this
158:37 

158:37 quarter or next quarter on asset
158:40 

158:40 operations handoff. So again that
158:43 

158:43 specific move from once we get done with
158:45 

158:45 construction well what do we do with it
158:47 

158:47 now? So we are continuing to try to
158:50 

158:50 build out and uh and further detail out
158:54 

158:54 the standard to support all the
158:57 

158:57 different needs that the that we the DOS
158:59 

158:59 have. So just a quick update.
159:02 

159:02 >> Yeah. Great.
159:04 

159:04 >> Can I add to that for a minute too,
159:06 

159:06 ma'am? Um
159:06 

159:06 >> yeah,
159:07 

159:07 >> because I think um it
159:09 

159:09 >> we on uh on Monday we're expecting to
159:12 

159:12 hear from Oklahoma DOT whose ADCMS grant
159:17 

159:17 includes looking at the process. I think
159:20 

159:20 IFC is great for um information exchange
159:25 

159:25 standardization, but process management
159:29 

159:29 standardization is really better covered
159:31 

159:31 by ISO 19650. And I think um uh Nathan's
159:36 

159:36 comment mentioned that. And what we're
159:39 

159:39 hoping to accomplish on Monday from
159:41 

159:41 Oklahoma DOT is hear about their ADCMS
159:45 

159:45 grant and maybe connect with what other
159:47 

159:47 DOS are doing. And then in the March
159:50 

159:50 session, we're hoping to workshop a
159:52 

159:52 little more deeply on that, how to use
159:55 

159:55 it, what it does, how to connect with it
159:58 

159:58 and build on it and get some things
160:01 

160:01 going around a collective implementation
160:04 

160:04 of ISO 19650.
160:06 

160:06 I think we've got some real good
160:08 

160:08 traction on implementation of IFC
160:11 

160:11 through the work of the poolled funds,
160:13 

160:13 but we really don't have much going on
160:16 

160:16 ISO 19650. So this could be a way to
160:19 

160:19 point towards that. I'd also add that um
160:23 

160:23 here in the US the ISO standard
160:27 

160:27 um have been the the mirror committee
160:30 

160:30 for those is run through Ashray. NIBs is
160:33 

160:33 in the process of working with Ashray on
160:35 

160:35 that to re-energize it and use it to
160:39 

160:39 advance ISO 19650 and other standards
160:42 

160:42 under that committee which does include
160:46 

160:46 um the IFC as well here in the US. So I
160:51 

160:51 just mention that I see Katie has her
160:53 

160:53 hand up. So hopefully I said that all uh
160:57 

160:57 correctly Katie, but please add on
160:59 

160:59 anything you'd like. No, no, Roger, you
161:02 

161:02 did. I I just wanted to tell you, you
161:04 

161:04 did state that correctly. And what I
161:06 

161:06 would say about ISO 19650, you know,
161:08 

161:08 it's been really successfully
161:11 

161:11 implemented in other countries. You
161:13 

161:13 know, it's just about um how to manage
161:16 

161:16 your BIM processes and it is a totally
161:20 

161:20 new concept to Oklahoma. This is not
161:23 

161:23 something that we've ever done before,
161:25 

161:25 but that's because we were never really
161:28 

161:28 focused on
161:30 

161:30 managing data before, right? We were
161:33 

161:33 managing information on paper, but not
161:37 

161:37 really data. But ISO 19650 gives us a a
161:41 

161:41 framework for actually managing
161:45 

161:45 data in a data life cycle and not
161:49 

161:49 um on paper. So um we have
161:54 

161:54 definitely started to look at how do we
161:58 

161:58 really utilize that to our advantage
162:00 

162:00 because ultimately what we're going
162:03 

162:03 towards is database processes. Right. So
162:10 

162:10 >> yeah, thanks Katie and and come join us
162:12 

162:12 on Monday afternoon if you're if uh
162:16 

162:16 Blizzard allowing uh to um uh hear more
162:20 

162:20 about that.
162:25 

162:25 Thanks uh May I thought it'd be good to
162:27 

162:27 get that in there too. And thanks to
162:31 

162:31 Will for the update on IFC,
162:35 

162:35 >> Devin.
162:37 

162:37 >> Yeah. Um, I love the way Katie just uh
162:42 

162:42 established that and I would be
162:44 

162:44 interested to hear, maybe not in this
162:46 

162:46 setting right now because I know we got
162:48 

162:48 limited time, but I'd be interested to
162:49 

162:49 have a conversation
162:51 

162:51 from with maybe some of the
162:52 

162:52 organizations that have started down a
162:54 

162:54 digital delivery path and then things
162:56 

162:56 like ISO 19650 and other standards are
162:59 

162:59 coming up and you're finding that you're
162:60 

163:00 having to shift from where you've
163:02 

163:02 started because this is, you know, I'll
163:05 

163:05 I'll share this. This has been a topic
163:07 

163:07 of discussion within Calrans of some of
163:10 

163:10 the file format exchange that has been
163:13 

163:13 worked on for the better part of 10
163:16 

163:16 years as you know we've been doing some
163:18 

163:18 level of digital delivery but this
163:22 

163:22 emphasis now on BIM processes and having
163:25 

163:25 things like ISO
163:27 

163:27 uh coming into play
163:30 

163:30 how is that impacting others where
163:31 

163:31 you're finding that
163:34 

163:34 you know I've had many conversations
163:36 

163:36 with Katie, you know, they're kind of
163:37 

163:37 starting from scratch, so they're able
163:39 

163:39 to kind of start from the beginning. But
163:40 

163:40 if you've already gone down a path, how
163:43 

163:43 is that impacting how you have to shift?
163:46 

163:46 And if it's not it's not a clear shift
163:48 

163:48 on all projects all at once, how that's
163:51 

163:51 getting managed for implementing on
163:54 

163:54 certain projects versus your legacy
163:57 

163:57 process on others. So maybe that's
163:60 

163:60 something we can that's a big topic I
164:02 

164:02 recognize and we could talk about that
164:03 

164:03 in the future.
164:05 

164:05 I think that's that that perfectly goes
164:07 

164:07 with what we want to talk about on
164:09 

164:09 Monday afternoon and then hopefully dig
164:11 

164:11 more deeply into in the March uh
164:14 

164:14 meeting. So that's great
164:18 

164:18 Deon and yeah we'll keep tracking with
164:20 

164:20 you on that.
164:21 

164:21 >> Okay. Uh the Monday meeting is going to
164:23 

164:23 be recorded correct? So there can be a
164:26 

164:26 recording sent out. Okay. Because I
164:28 

164:28 correct
164:29 

164:29 >> I won't be available on Monday. We have
164:30 

164:30 a we have a planning session uh for our
164:34 

164:34 summit that's coming up in a few in two
164:36 

164:36 months.
164:47 

164:47 Well, um Okay, Matt, do you want to uh
164:50 

164:50 look at the
164:53 

164:53 um schedule or the um there's a little
164:57 

164:57 input there for the agenda for March?
164:59 

164:59 But, um and I know another way we can we
165:02 

165:02 can maybe get what we can today with the
165:04 

165:04 time we have. I did allow a little time
165:06 

165:06 also at the end of Thursday for us to
165:08 

165:08 revisit this topic based on what we've
165:11 

165:11 learned overall. So, um, yeah, just to
165:14 

165:14 keep in mind,
165:16 

165:16 >> yeah, we can we can keep coming back to
165:18 

165:18 that. Um, these couple items here
165:21 

165:21 remaining and in the remaining of the
165:24 

165:24 meetings that we have scheduled um to
165:27 

165:27 help us put together a strategy for our
165:31 

165:31 agenda and
165:33 

165:33 for the GIS event. Um
165:37 

165:37 just uh again a reminder here in mural
165:41 

165:41 on the slide that Roger's on and if you
165:43 

165:43 either want to follow his pointer or
165:46 

165:46 dive in there um we've got the you know
165:49 

165:49 the details on the the next uh hybrid
165:54 

165:54 meeting that we're planning to have in
165:55 

165:55 person as part of GIST. Um there is a
165:58 

165:58 very preliminary very very preliminary
166:01 

166:01 agenda. So that's uh likely to change um
166:06 

166:06 between now and then, but we do have two
166:09 

166:09 half-day sessions, the Thursday
166:11 

166:11 afternoon and the Friday morning uh for
166:15 

166:15 us to meet in person and continue the
166:17 

166:17 dialogue. Um, if there's uh something
166:20 

166:20 that you feel like is important for the
166:23 

166:23 group to be aware of or bring up or have
166:25 

166:25 a dialogue on, again, the mural, um, you
166:29 

166:29 know, we want you to to go in there and,
166:32 

166:32 you know, put a sticky note or something
166:33 

166:33 or highlight um, for us to be able to
166:36 

166:36 digest and dialogue with our our members
166:39 

166:39 as well as we work out the agenda for
166:42 

166:42 the next one. Um and then for you know
166:45 

166:45 planning purposes and and I know a lot
166:48 

166:48 of our members had some conflicts and
166:50 

166:50 had to drop off but uh in the remaining
166:53 

166:53 time. Oh and you know specifically kind
166:57 

166:57 of ask um you know again if you can help
167:00 

167:00 us to to collaborate on any kind of
167:03 

167:03 items that are coming up. Um, right
167:06 

167:06 below that space where Roger is, uh, is
167:09 

167:09 an opportunity to highlight any of the
167:13 

167:13 upcoming meetings that you are aware of,
167:15 

167:15 whether it's just, you know, within your
167:17 

167:17 state or regionally or things that
167:19 

167:19 you're actively engaged with that would
167:22 

167:22 preclude you from being able to
167:24 

167:24 participate with us in this group. um
167:27 

167:27 you know, we we're trying to crowdsource
167:29 

167:29 that information to help us thread
167:31 

167:31 thread that needle on scheduling and
167:34 

167:34 minimizing conflicts. Um if we take a
167:37 

167:37 look at uh us having our next meeting in
167:41 

167:41 March as part of the GIST event and then
167:44 

167:44 through the rest of the year, um how we
167:47 

167:47 want to split that up. I know Jacob had
167:50 

167:50 mentioned um uh previously
167:54 

167:54 that the next I HEAP meeting for this
167:58 

167:58 year, the 2026 I HEAP meeting um and
168:02 

168:02 I'll put the link in there in the chat
168:04 

168:04 for everybody again for those that maybe
168:06 

168:06 aren't familiar with it is a a pretty
168:09 

168:09 large event that has been you know not
168:13 

168:13 only a combination of trade show uh and
168:16 

168:16 vendors um in this area of digital
168:19 

168:19 delivery, but I've you know been
168:20 

168:20 involved in this one for some time. I've
168:22 

168:22 only recently become uh involved in IHEA
168:26 

168:26 and and was uh able to attend. Um I
168:30 

168:30 wasn't able to attend the last one but
168:31 

168:31 the previous one before that uh Jacob
168:35 

168:35 had offered and you know as as being a
168:38 

168:38 member of the DDSG himself and Texas
168:41 

168:41 being the host of the next meeting
168:44 

168:44 coming up is that would be a potential
168:46 

168:46 uh venue that we could again host the
168:49 

168:49 DDSG um and if that would be ideal for
168:54 

168:54 the members. Um I know many of you, you
168:57 

168:57 know, go to to uh I HEAP, but we would
169:01 

169:01 certainly have to figure out how we
169:02 

169:02 would schedule so that we're not
169:05 

169:05 conflicting with your other activities
169:07 

169:07 and and um looking for much more time uh
169:11 

169:11 for us to dedicate to the collaboration
169:14 

169:14 uh rather than just the you know one
169:16 

169:16 session short 3 to four hours that we
169:19 

169:19 had at the last time at IEP. So, we may
169:22 

169:22 have to piggy back like at the end again
169:24 

169:24 as part of GIST
169:26 

169:26 um where you would, you know,
169:28 

169:28 potentially need to stay or we would
169:31 

169:31 hope that you would be able to stay uh a
169:34 

169:34 couple days later or if that's not
169:38 

169:38 something that's desirable because you
169:39 

169:39 already got too much going on with I
169:41 

169:41 heap for us to maybe target something
169:44 

169:44 separate. Um if you know that would be
169:48 

169:48 at the beginning of December uh for
169:50 

169:50 Austin, Texas's high heap which would
169:53 

169:53 then if we were to have another virtual
169:55 

169:55 exchange somewhere between March GIST
169:59 

169:59 meeting and the IHEA in December puts us
170:02 

170:02 at like end of July,
170:05 

170:05 beginning of August for the next virtual
170:10 

170:10 uh only meeting kind of in between those
170:12 

170:12 two uh in-person meetings.
170:15 

170:15 And so if there's something, you know,
170:17 

170:17 in July, August that would be a
170:20 

170:20 conflict, um, we certainly would want to
170:23 

170:23 be aware of that and either hear from
170:25 

170:25 you now about those or, um, have you
170:28 

170:28 follow up and go into the mural to
170:30 

170:30 identify those. Um, but I I will pause
170:33 

170:33 there and open it up to to the members
170:36 

170:36 that are still online to maybe
170:38 

170:38 contribute on if you like the idea I
170:41 

170:41 heap or not. If you like the idea of us
170:44 

170:44 continuing to try and piggy back on
170:46 

170:46 events with are I will say are not
170:50 

170:50 without their own logistic challenges
170:52 

170:52 for us to piggyback. There are good
170:55 

170:55 things that certainly come out of that
170:57 

170:57 for us to collaborate with other
170:58 

170:58 communities or if it's something that a
171:01 

171:01 lot of our members are going to be
171:02 

171:02 attending already. Um, but then to try
171:06 

171:06 and make sure we have enough time
171:07 

171:07 dedicated to collaborate and start
171:11 

171:11 picking up, you know, action items or or
171:13 

171:13 task group activities
171:16 

171:16 uh to where, you know, we're not just
171:18 

171:18 kind of at the very end of the week and
171:20 

171:20 people are tired and still need to
171:22 

171:22 travel home. there are all those other
171:25 

171:25 things that uh are challenges to
171:27 

171:27 navigate as well where potentially us
171:30 

171:30 having a dedicated time in facility you
171:33 

171:33 know whether it's at a do complex or
171:36 

171:36 here at you know our R&D facility in
171:38 

171:38 Northern Virginia or something else um
171:41 

171:41 is is another option and another
171:43 

171:43 direction to go but let me stop I see
171:45 

171:45 Katie already has her hand up so please
171:48 

171:48 go ahead Katie
171:49 

171:49 >> I did I was going to say that committee
171:51 

171:51 on design was in August last year but
171:53 

171:53 Somebody was typing. I don't know who
171:55 

171:55 put that in there. Um, but it looks like
171:57 

171:57 it's August 16th through 20 in De
171:59 

171:59 Moines. Is I don't I don't know.
172:03 

172:03 I haven't seen that before, but that's
172:06 

172:06 really great information, whoever put
172:08 

172:08 that there. Thank you. And then I don't
172:10 

172:10 know if um Jacob is still on this call
172:14 

172:14 or not, but I'm sure I heap we can find
172:18 

172:18 a way to carve out some time for you.
172:20 

172:20 I'm sure we can work on that. Okay,
172:24 

172:24 I see uh Mark in the chat has an item
172:28 

172:28 he's working on. Uh the late January
172:33 

172:33 and early February
172:36 

172:36 just coming around the corner, I see. Um
172:43 

172:43 and there's a a link to register, I
172:46 

172:46 think. Thank you, Mark, for passing on
172:49 

172:49 that information. I'm sure that'll
172:51 

172:51 generate some interest. Um,
172:58 

172:58 do how many of the members still
173:01 

173:01 participate and are going to anticipate
173:04 

173:04 being on site in March um in Chicago?
173:11 

173:11 You could maybe just show a hands or
173:16 

173:16 Katie's will is
173:19 

173:19 I plan to be as long as I get approval.
173:26 

173:26 Um okay. I I I'm hoping we get, you
173:31 

173:31 know, some of the GIS people to to stay
173:33 

173:33 over and participate and engage with us.
173:36 

173:36 I think that's uh you know kind of two
173:39 

173:39 communities that have a natural synergy
173:42 

173:42 uh in this space.
173:46 

173:46 Um we'll see how that works. Uh I again
173:50 

173:50 realize that us having our portion not
173:53 

173:53 to conflict with theirs and take away
173:55 

173:55 from their meetings. You know we had to
173:58 

173:58 go Thursday uh afternoon Friday morning.
174:01 

174:01 Hopefully that's not too big of a
174:03 

174:03 challenge for people getting home Friday
174:04 

174:04 afternoon out of Chicago and um the
174:08 

174:08 weather cooperates, etc. Um
174:12 

174:12 maybe we'll have more dialogue and
174:14 

174:14 feedback on if that
174:17 

174:17 is uh ideal for everybody or not. Is is
174:20 

174:20 I heap does I heap sound like a good
174:22 

174:22 target for the next inperson? It would
174:25 

174:25 be the first week in December
174:28 

174:28 kind of, you know, squeezed in between
174:31 

174:31 Thanksgiving and Christmas.
174:35 

174:35 Any thoughts?
174:38 

174:38 You're all very busy. I know.
174:44 

174:44 >> Sometimes December is a tough travel
174:46 

174:46 month for people.
174:49 

174:49 >> Yep. Yeah, I know.
174:53 

174:53 Katie, you expect to be at I Heap
174:55 

174:55 though?
174:55 

174:55 >> Oh, yeah. I will be I will be there.
174:58 

174:58 Yeah.
174:59 

174:59 >> Yeah. Any others?
175:03 

175:03 Cassidy or Devon?
175:07 

175:07 >> Um I will not be able to attend in
175:10 

175:10 person the March. Um
175:14 

175:14 but if there's the virtual option, I'll
175:16 

175:16 be able to attend. We have March uh is a
175:22 

175:22 for Calrans is a tough year. Um
175:24 

175:24 >> yeah,
175:26 

175:26 >> there's a just a number of things that
175:28 

175:28 happen all in that month. Um
175:30 

175:30 >> I would also say, you know, I agree with
175:33 

175:33 Katie like oftentimes December is a
175:35 

175:35 struggle, but maybe that week of I heap
175:37 

175:37 is potentially better than most. um for
175:41 

175:41 the meetings that we're going to do in
175:43 

175:43 person each year. I don't know about the
175:45 

175:45 rest of the committee members, but I
175:48 

175:48 would appreciate if we could just get on
175:50 

175:50 a schedule that we could plan on year in
175:52 

175:52 and year out that these are the these
175:54 

175:54 are the in-person sessions and that
175:57 

175:57 might give us the ability to
175:60 

175:60 get any planning and approval steps in
176:02 

176:02 place in advance and, you know, get our
176:06 

176:06 travel blanket
176:08 

176:08 kind of stuff, you know, figured out.
176:10 

176:10 uh you know even though it might be
176:14 

176:14 supported by
176:16 

176:16 uh national funding,
176:19 

176:19 you know, we still actually get
176:20 

176:20 approvals for the travel part of it in
176:22 

176:22 our time or at least I know I do.
176:26 

176:26 >> Yeah. Yeah. Thanks, Devin. That that's
176:29 

176:29 helpful. I I think we need to shop this
176:32 

176:32 with the other members because if if
176:34 

176:34 that's a a a challenge that everybody's,
176:37 

176:37 you know, dealing with, then that
176:39 

176:39 perhaps might be our best pivot is to
176:45 

176:45 >> have some times and locations just
176:47 

176:47 established and done,
176:48 

176:48 >> right? And if we could get on a cadence,
176:51 

176:51 I think that makes it real easy. And if
176:52 

176:52 it's matched up with something else, it
176:54 

176:54 makes it real easy to say, "Yeah, every
176:57 

176:57 year during BIM week, we're going to
176:59 

176:59 have a day that is the digital delivery,
177:02 

177:02 you know, the DDSG." And every year
177:05 

177:05 during another one, it's, you know,
177:07 

177:07 there's a day that is the DDSG. And that
177:09 

177:09 also gives us the ability to potentially
177:11 

177:11 attend those other sessions as well.
177:16 

177:16 >> Yeah, I support that.
177:20 

177:20 Do you do you feel how do you feel about
177:22 

177:22 BIM week? I see Jim um put it in there
177:26 

177:26 too and it um um yeah there's a lot of
177:29 

177:29 similar activities there which can be
177:32 

177:32 both a plus and a minus but it's a good
177:35 

177:35 opportunity where there are a lot of
177:37 

177:37 >> people doing things uh at the same time.
177:40 

177:40 >> Is that
177:42 

177:42 >> Roger that dates established right?
177:44 

177:44 Sorry,
177:45 

177:45 >> it hasn't been fully pinned down, but
177:47 

177:47 the tenative plan is that first week of
177:50 

177:50 November. The location is still under
177:53 

177:53 consideration based on the conversation
177:56 

177:56 last week.
177:58 

177:58 >> Okay.
177:58 

177:58 >> And that's the most likely date unless
178:00 

178:00 something would go haywire, I guess. I I
178:06 

178:06 just think um you know if we match up
178:09 

178:09 you know the the essence of what the
178:11 

178:11 DDSG is focused at trying to solve if
178:15 

178:15 we're matching up with some events that
178:18 

178:18 are more aligned I I know that there's a
178:20 

178:20 lot of the committee on construction
178:22 

178:22 committee on maintenance those type of
178:24 

178:24 efforts um but you know not speaking for
178:28 

178:28 all the members not all of us are
178:30 

178:30 necessarily on the committee on
178:31 

178:31 construction so it might not be
178:33 

178:33 something that we would traveled to. But
178:36 

178:36 if it's something that's, you know,
178:38 

178:38 maybe aligns more with the focus based
178:40 

178:40 on our charter. Um,
178:44 

178:44 I think, you know, that to me that would
178:46 

178:46 be more interesting.
178:49 

178:49 >> Um, and you know, there are tend to be a
178:52 

178:52 couple of them spaced out. You know, BIM
178:54 

178:54 week is a perfect example. We also stay
178:55 

178:55 very close in touch with what's
178:56 

178:56 happening with the pulled fund studies,
178:58 

178:58 what's happening with a couple of those
178:60 

178:60 committees that meet there. So, it's,
179:01 

179:01 you know, much more it's it's closely
179:04 

179:04 aligned with this group's focus area. As
179:06 

179:06 far as another one sometime in spring, I
179:09 

179:09 don't I don't know for sure. I put a
179:11 

179:11 couple of other ideas in there myself
179:13 

179:13 and some of the other notes of even if
179:16 

179:16 it's not a federal or a government
179:20 

179:20 event, but if it's something that you
179:22 

179:22 know it's a a vendor event that gives an
179:24 

179:24 opportunity for these folks to also
179:26 

179:26 attend and get a lot of other
179:27 

179:27 interaction like at Trimble Dimensions
179:30 

179:30 or the Ezri U it's you know maybe
179:32 

179:32 there's some advantages of there's this
179:36 

179:36 the the the committee group but then you
179:39 

179:39 can also have that other interaction and
179:42 

179:42 experience with what's happening in the
179:44 

179:44 rest of this space.
179:47 

179:47 >> Yep. Thanks, Devin. Appreciate that.
179:50 

179:50 >> Right.
179:50 

179:50 >> I do just want to call attention, sorry,
179:52 

179:52 Matt, that it is in fact it's 3:01 now.
179:55 

179:55 Um, and so people are starting to drop
179:57 

179:57 off. So, if there's any um,
179:60 

179:60 >> you know, f I mean, we can keep going,
180:01 

180:01 but if there's final notes, uh, that
180:03 

180:03 you'd like to give on everything, um,
180:06 

180:06 now would be the time to do so. Uh, I
180:08 

180:08 just want to say before everybody leaves
180:10 

180:10 that if you want to take an opportunity
180:11 

180:11 to later today or or at any other time
180:14 

180:14 to go on the mural and leave a comment
180:16 

180:16 on anything we talked about today, I
180:18 

180:18 would really appreciate it. Um, this is
180:19 

180:19 an excellent excellent location to uh
180:22 

180:22 collaborate and leave opinions and
180:24 

180:24 comments and to keep up to date. Uh, I
180:26 

180:26 want to drag your attention really quick
180:28 

180:28 to the very top of the mural that uh
180:31 

180:31 over the course of the chat I've tried
180:32 

180:32 my best to collect all of the links that
180:34 

180:34 were posted that's at the very top. um
180:39 

180:39 under you know the big green today's
180:41 

180:41 meeting right there. So that's I believe
180:42 

180:42 all the links that have been been uh
180:44 

180:44 posted. Um at least from what I've seen
180:48 

180:48 uh of course there's all kinds of
180:50 

180:50 different feedback and things. Uh the
180:52 

180:52 best place to leave feedback if you just
180:53 

180:53 have general comments would be in this
180:55 

180:55 general meeting comments. A lot of
180:56 

180:56 people have already left them which is
180:58 

180:58 fantastic. Thank you very much for doing
180:59 

180:59 that. Um
181:01 

181:01 yeah, if there's anything you want to
181:02 

181:02 see improved for the next meeting or
181:04 

181:04 meetings in the future via mural or
181:06 

181:06 otherwise, please uh do let us know uh
181:09 

181:09 here. Uh thank you very much. If yeah,
181:12 

181:12 if there's any other meetings that you
181:14 

181:14 want to add, uh please go look at the uh
181:17 

181:17 DDSG scheduling section and leave them
181:19 

181:19 there. Uh we've tried to pull in
181:20 

181:20 everything. You know, if people aren't
181:22 

181:22 doing real stuff, we've been trying to
181:24 

181:24 do that. But anyways, thank you very
181:25 

181:25 much. I very appreciate it. Uh back to
181:28 

181:28 you, Matt. Yeah, thanks Rackley.
181:30 

181:30 Appreciate that too as well. Um,
181:32 

181:32 apologize for running over. I try not to
181:34 

181:34 do that um uh on a regular basis. We
181:38 

181:38 will have other opportunities to
181:41 

181:41 dialogue throughout the rest of the
181:43 

181:43 meetings Monday and Wednesday. Um, with
181:46 

181:46 regards to scheduling, Roger and I will
181:50 

181:50 uh circle back with the membership um as
181:53 

181:53 far as uh planning and schedules in
181:55 

181:55 future as we digest um the events that
181:59 

181:59 are posted on the mural and come up with
182:02 

182:02 a plan on that one. Uh we will see you
182:05 

182:05 on Monday. Uh just a reminder, the next
182:07 

182:07 session is at noon Eastern on Monday and
182:10 

182:10 if you haven't registered for that
182:12 

182:12 already. Um it is on the DDSG hub
182:16 

182:16 registration site. Um so we will see you
182:19 

182:19 Monday. Thanks for everybody.
182:22 

182:22 >> Thanks everyone. Thanks Matt.
182:24 

182:24 >> Thanks.
182:25 

182:25 >> Good to see you all. Good to be seen.
182:45 

182:45 Hey, Matt, are you still there by
182:46 

182:46 chance?
182:49 

182:49 >> I am.
182:51 

182:51 >> Uh, one
182:53 

182:53 just one note from the from the other
182:55 

182:55 side from this side. Um, I don't know if
182:59 

182:59 it's maybe how you set it up and this
183:01 

183:01 functionality is not there, but I
183:02 

183:02 noticed that the uh like the expressions
183:07 

183:07 ability of, you know, thumbs up,
183:09 

183:09 clapping, all that kind of stuff was
183:11 

183:11 turned off.
183:13 

183:13 Um,
183:16 

183:16 the only like the only option that uh
183:19 

183:19 participants have is like to raise their
183:21 

183:21 hand or not. So, I don't know if that's
183:23 

183:23 a functionality that is just not part of
183:26 

183:26 this this setup with it being more
183:28 

183:28 webinar focused. Um, but I you know, I
183:32 

183:32 don't know if that's something you want
183:33 

183:33 to think about maybe making sure it's
183:36 

183:36 enabled and you can just get some more
183:38 

183:38 general
183:39 

183:39 understanding of where the
183:40 

183:40 conversation's going when people can
183:42 

183:42 just, you know, throw a thumbs up or
183:44 

183:44 something.
183:45 

183:45 >> Gotcha. Yeah. I don't know. I'll have to
183:47 

183:47 ask Brackley might know if he's still
183:49 

183:49 on.
183:50 

183:50 >> I'm still here. is that the
183:51 

183:51 >> if I'm not here, the meeting's dead.
183:54 

183:54 >> Good point.
183:55 

183:55 >> Good point. Good point.
183:58 

183:58 >> Um, in the beginning, uh, how people
184:01 

184:01 weren't able to communicate at all via
184:03 

184:03 chat. I mean, there's a setting where
184:04 

184:04 attendees can chat, you know, with
184:06 

184:06 everybody. Um, as far as using emojis,
184:10 

184:10 there's no, um,
184:13 

184:13 >> well, you can put the emojis in the
184:15 

184:15 chat, but I was just thinking of like,
184:17 

184:17 you know, the simple just like hitting a
184:19 

184:19 thumbs up or the clapping. So, it kind
184:20 

184:20 of like, you know, expand.
184:22 

184:22 >> Oh, you mean like uh Oh, I see. Um I
184:26 

184:26 mean, I don't even know if that's
184:28 

184:28 something that Zoom does.
184:31 

184:31 >> Yeah, I trouble adding those in the chat
184:34 

184:34 to somebody's comment that I liked. You
184:36 

184:36 could do it
184:38 

184:38 >> in in uh sequence, but you couldn't go
184:40 

184:40 to their comment and like do it
184:43 

184:43 >> on I don't know if that's a restriction
184:47 

184:47 >> webinar or what. So I I don't know. I
184:51 

184:51 I've I've been in a lot of We don't use
184:54 

184:54 Zoom at Cow Trans. We use Teams and
184:56 

184:56 WebEx, but
184:57 

184:57 >> Right.
184:58 

184:58 >> those definitely allow it. Teams and
184:60 

184:60 WebEx do. Um
185:02 

185:02 >> I've had other Zoom meetings where even
185:05 

185:05 if it's just,
185:07 

185:07 >> you know, down in the the raise hand
185:10 

185:10 there's a little carrot up and usually
185:11 

185:11 with that it gives you a list of it
185:14 

185:14 gives you the other things you can do,
185:16 

185:16 but that's not present. And to Roger.
185:20 

185:20 >> Yeah. And then to your point, Roger, I
185:22 

185:22 have because same thing like I was
185:23 

185:23 trying to like as I was trying to keep
185:24 

185:24 up with the chat somewhat some of those
185:27 

185:27 comments of like, oh man, like I want to
185:28 

185:28 give a thumbs up to that to like high
185:30 

185:30 >> I'd like to post that one up
185:32 

185:32 >> or reply to or reply to it because that
185:35 

185:35 used to be a function that I recall. But
185:37 

185:37 the way you have this set up with um it
185:42 

185:42 being more webinar style, maybe that's
185:44 

185:44 not something that's part of the webinar
185:45 

185:45 style. Maybe that's why.
185:47 

185:47 >> Ah, yeah, that's true. There was an
185:48 

185:48 option to convert this to a meeting, but
185:50 

185:50 then a lot of the sort of control
185:53 

185:53 features we would lose,
185:55 

185:55 >> right?
185:55 

185:55 >> Um,
185:56 

185:56 >> that can get chaotic,
185:57 

185:57 >> which would get when we had, you know,
185:58 

185:58 we we had a good turnout. We had over
186:00 

186:00 220ish people on board, which was which
186:03 

186:03 is fantastic. Um, it was a lot of people
186:06 

186:06 and I I just I'm trying to think, you
186:09 

186:09 know, if if it was just a meeting that
186:11 

186:11 means everybody can control whether
186:12 

186:12 they're speaking or not or their cameras
186:14 

186:14 on or not, which is fine if everybody is
186:17 

186:17 a upstanding, you know, technically
186:20 

186:20 literate individual.
186:22 

186:22 >> But, you know, I get I get for this like
186:24 

186:24 you Yeah, you got to be careful with
186:25 

186:25 that. I just as you were setting up the
186:28 

186:28 um the webinar I was just I was just
186:30 

186:30 pointing that out of like maybe in the
186:33 

186:33 process of establishing it that those
186:35 

186:35 features might be something that you
186:36 

186:36 have to enable as well. So I just I just
186:40 

186:40 wanted to give you a perspective from
186:41 

186:41 from this side being somebody on the
186:45 

186:45 experience side that there were a number
186:47 

186:47 of times I tried to do that and it just
186:50 

186:50 like
186:52 

186:52 >> I stopped I stopped trying to figure it
186:54 

186:54 out for a while but maybe for the first
186:56 

186:56 like 30 or 40 minutes I was trying to
186:57 

186:57 figure out
186:59 

186:59 >> the same thing
187:01 

187:01 >> even on my end I I don't have the option
187:03 

187:03 to do that. I mean, when I go back in
187:05 

187:05 and I set up the the or I edit and
187:08 

187:08 adjust the webinar for Monday, I will
187:10 

187:10 definitely scrape through all the
187:12 

187:12 settings and see if that's something
187:13 

187:13 that's an option. I am uncertain. I
187:16 

187:16 don't know why that wouldn't be on by
187:17 

187:17 default, but um yeah,
187:19 

187:19 >> I'll I'll definitely check it check it
187:21 

187:21 thoroughly. Um and we'll see.
187:23 

187:23 >> But I appreciate the note for sure.
187:25 

187:25 >> Oh, yeah. And thank you thank you for
187:28 

187:28 keeping this moving forward. It really
187:30 

187:30 is appreciated. I know there's a lot of
187:31 

187:31 effort that goes into trying to organize
187:34 

187:34 things like this. So, uh want to make
187:37 

187:37 sure you guys heard that at least from
187:38 

187:38 me that it is appreciated and
187:42 

187:42 >> well, we we definitely we appreciate
187:44 

187:44 your engagement and your uh willingness
187:47 

187:47 to be vocal um and your grace and
187:50 

187:50 hanging in with us because
187:51 

187:51 >> I know we're not without without our
187:54 

187:54 challenges here as as we as we get
187:56 

187:56 propped up here. But, uh
187:58 

187:58 >> um yeah, thanks Devin. Really appreciate
187:60 

187:60 it.
188:00 

188:00 >> No problem, man. Yeah, this was just a
188:03 

188:03 little bit of info that you know you
188:05 

188:05 might have things like that the as as
188:08 

188:08 much as we've been in this virtual world
188:10 

188:10 of doing things a lot of people have
188:12 

188:12 just kind of deferred to being able to
188:13 

188:13 throw up a thumbs up or something like
188:15 

188:15 that. So yeah, just sharing that of um
188:20 

188:20 you know if if it's simply a setting
188:22 

188:22 like you might get a little bit more
188:24 

188:24 engagement from other people as well.
188:26 

188:26 Yeah,
188:26 

188:26 >> absolutely. If it's if it's setting
188:28 

188:28 it'll be on for next time for sure. I'll
188:30 

188:30 find out. Uh certainly
188:33 

188:33 >> are these are these going
188:34 

188:34 >> I tried to I tried to do the same thing
188:36 

188:36 Devin like I was trying to like react or
188:39 

188:39 like you know like reply to or copy
188:42 

188:42 paste like and but I will say that like
188:45 

188:45 when Federal Highway uses Zoom similarly
188:49 

188:49 I I it's been a little while since we've
188:51 

188:51 had one that I've been involved with but
188:53 

188:53 I think we've had similar kind of
188:55 

188:55 restrictions in that webinar.
188:58 

188:58 I don't know if we can get around it,
189:00 

189:00 but we will look into it because I think
189:02 

189:02 if we can still have the control where
189:05 

189:05 it's not just random chaos of everybody,
189:08 

189:08 but we can provide some of that
189:09 

189:09 functionality, it would be good if we
189:11 

189:11 can do that. Yeah.
189:12 

189:12 >> And and by all means, a little bit more
189:15 

189:15 control so it's not chaos is more
189:17 

189:17 important than the ability to have some
189:19 

189:19 of that added functionality. So, it's
189:21 

189:21 completely understood if it's just
189:23 

189:23 >> if it's just the way it goes,
189:24 

189:24 >> right? Um, are these
189:27 

189:27 >> are these going to continue to be a
189:28 

189:28 little bit more of a public forum style
189:31 

189:31 too where we have, you know, the members
189:32 

189:32 that are in attendance, but we could
189:34 

189:34 still have, you know, another 100 to 200
189:37 

189:37 people that are attending or is that
189:38 

189:38 just specifically
189:40 

189:40 maybe I'm not remembering something from
189:42 

189:42 one of our previous meetings. Was that
189:43 

189:43 just specifically this one which was
189:45 

189:45 meant to be like a bigger audience?
189:48 

189:48 >> No, we we we've kind of been mandated,
189:52 

189:52 if you will, to be kind of open and
189:53 

189:53 public. um with the events. So for the
189:57 

189:57 main events, they will be of this nature
190:01 

190:01 um where there will be an open virtual
190:03 

190:03 component. Now if you and the DDSG feel
190:07 

190:07 like there's a need for us to have
190:09 

190:09 certain whatever business items or
190:12 

190:12 something that's a little bit maybe more
190:14 

190:14 sensitive, I think we can certainly
190:16 

190:16 figure out a way to do that and make
190:20 

190:20 sure that we're addressing that need.
190:22 

190:22 Yeah, it it might not be a bad idea for
190:25 

190:25 the group to talk about if we want to
190:27 

190:27 have a portion that would be a closed
190:29 

190:29 session that allows for, you know, a
190:32 

190:32 little bit more of highlighting
190:35 

190:35 challenges and struggles that may not be
190:37 

190:37 presented as much publicly. Um, and
190:40 

190:40 opportunity, you know, for the folks to,
190:44 

190:44 you know, identify ways to work together
190:46 

190:46 to solve those. And you know, not that
190:49 

190:49 all the challenges are so horrible that
190:53 

190:53 they shouldn't be, but often times it's
190:56 

190:56 it's uh hard to bring things up when
190:58 

190:58 it's, you know, that many people. I uh
191:02 

191:02 I think there were a few things a few
191:03 

191:03 things I mentioned earlier on and I I I
191:06 

191:06 might have missed the part and then
191:07 

191:07 looked at the when I opened up the
191:09 

191:09 participants and I saw that there were
191:10 

191:10 another, you know, 150 170 other parts.
191:15 

191:15 I was like, "Oh,
191:17 

191:17 forgot about that piece.
191:19 

191:19 >> Yeah,
191:21 

191:21 >> I've heard that same comment from a few
191:23 

191:23 of the other members. So, I think it's
191:25 

191:25 something that probably needs to be
191:28 

191:28 figured out as we go forward. Yeah.
191:31 

191:31 >> Okay.
191:33 

191:33 Anyway, I appreciate appreciate the
191:36 

191:36 effort and the work, gentlemen. I will
191:38 

191:38 let you go. I know we were supposed to
191:39 

191:39 end 12 minutes ago, but thank you.
191:41 

191:41 Appreciate it.
191:43 

191:43 >> Yeah, absolutely.
191:45 

191:45 >> Yeah. Thanks, Kevin. I'm just happy uh
191:47 

191:47 people used the mural so much. Um you
191:49 

191:49 know, we got a lot of good
191:50 

191:50 >> really worked out, I think.
191:51 

191:51 >> Well, I mean, it's just compared to what
191:53 

191:53 it was the the last mural I saw that was
191:56 

191:56 put together. Um this one was a little
191:58 

191:58 bit more controlled and and I think we
192:00 

192:00 got a lot of good feedback and uh
192:02 

192:02 especially with the menty survey. I
192:04 

192:04 mean, 100 people, it's definitely like a
192:05 

192:05 50% or 100% increase to what it was last
192:08 

192:08 time at I Heat. That may just be because
192:10 

192:10 it's a fully virtual and they almost
192:12 

192:12 don't have a choice. Uh
192:14 

192:14 >> yeah,
192:15 

192:15 >> but uh I mean I'm I couldn't be more
192:17 

192:17 pleased with the digital aspect of this.
192:19 

192:19 Uh people were very open to leaving
192:21 

192:21 comments and and getting information and
192:23 

192:23 also from chat. So I'm
192:24 

192:24 >> from some of from some of the different
192:27 

192:27 just a you know a tidbit of information
192:29 

192:29 you can you know take it or leave it.
192:30 

192:30 You know, the mirror boards are great,
192:32 

192:32 but the more you can do as mentter type
192:35 

192:35 of things, I think you're going to get
192:37 

192:37 more engagement out of that even than
192:39 

192:39 the mirror board because that's just
192:41 

192:41 something that is so easy for somebody
192:43 

192:43 to just simply tap on. We've used that
192:46 

192:46 at our our annual summit. We use that as
192:49 

192:49 a tool to capture all kinds of stuff
192:51 

192:51 from the audience. We use that to
192:53 

192:53 minimize how much we have to run a
192:55 

192:55 microphone around the room just to have
192:56 

192:56 people ask questions. instead have them
192:58 

192:58 put it into menty meter and we could
192:60 

192:60 just have somebody repeat it and you
193:01 

193:01 know it's like the efficiency you can
193:03 

193:03 get out of it but it's so easy to do
193:04 

193:04 something like that. Um you know the
193:08 

193:08 more you do that I think you're we're
193:10 

193:10 still going to get even more information
193:13 

193:13 and using Miro as a way to just follow
193:15 

193:15 up on it be great. So like what you guys
193:17 

193:17 did is perfect I think.
193:21 

193:21 Yeah, we do have people online still.
193:24 

193:24 Probably they might have been on on hold
193:26 

193:26 or or forgot or whatever or they're
193:29 

193:29 still listening. Um
193:30 

193:30 >> yeah, I mean, you know, the webinar is
193:33 

193:33 still ongoing and everything is still
193:34 

193:34 being, you know, recorded. Um just FYI.
193:38 

193:38 Um
193:39 

193:39 >> yeah, so well, but I don't think we uh
193:42 

193:42 we were just talking about how best to
193:44 

193:44 use the the technology. So that's all
193:46 

193:46 good. the the member part we can, you
193:49 

193:49 know, we might need to talk more about.
193:51 

193:51 So, I think we're good.
193:53 

193:53 >> Okay.
193:54 

193:54 >> Yeah.
193:56 

193:56 >> I don't think any of us forgot and
193:57 

193:57 started picking our nose. So,
194:01 

194:01 >> thanks, gentlemen. Appreciate it.
194:03 

194:03 >> Absolutely.
194:03 

194:03 >> Thanks, Devin.
194:05 

194:05 >> Bye.
194:06 

194:06 >> Thank you, everyone.
194:07 

194:07 >> Yeah. Thanks. Matt, do you want to find
194:10 

194:10 do you want to caucus for a few minutes
194:12 

194:12 after we can get on a teams or something
194:15 

194:15 if that would be helpful?
194:19 

194:19 >> Um, I can't I Yeah, I got a I got an
194:24 

194:24 appointment um that I got to leave for.
194:27 

194:27 >> Yeah, no problem. I think we've all had
194:28 

194:28 enough.
194:30 

194:30 >> So, okay, we'll um get set up for
194:34 

194:34 Monday. Maybe I will find a do a Monday
194:37 

194:37 morning time to talk and we can uh
194:41 

194:41 >> reconvene then. All right. All right.
194:44 

194:44 Thanks everybody. Thanks.
194:47 

194:47 >> Bye.