discuss and communicate a lot of these national efforts and interests and to help us for future planning.
You can leave that Mentimeter pole open after those first couple slides and hold it open until the end, where we've got, you know, remainder of feedback as far as what you saw today. We're also interested in
Making sure that what we're delivering is useful and meaningful and are topics that generate interest. We will come back to that towards the end as well, but just so you know, you can leave that open and respond to it after the fact as well.
Roger, I'll let you cover the mural
Okay, sure. Yeah, and I think the mentee you can access with the QR code or with the URL, which I think, Rakuten right
Yep, it is there, along with a little description.
Great. Then the mural for today, we've used the mural for our meetings and QR code for the mural was on the slide there and the link as well, which we'll put into the chat
And once you go there, you'll see the mural. You'll come into it like this. It's the mural for this meeting, so it has Monday and yesterday's meeting, and today's here. You can zoom in with your mouse or your touchpad
To get… move around and get to where you want to go. And the idea for the mural is we'll be tracking the meeting here, and this is also where we like to collect any comments, questions, anything you want to share with us
You can go right into the mural. There's a general area here. You can go right in. All you have to do is double-click in anywhere in the mural, and that'll open up a post-it note, and you can just start typing
Hello, this is great. Or something like that. And you can change the color, move it around. You grab this little thing here, you can move your host it wherever you want to change the size, etc. So please use that throughout the day as we go through
This session to communicate with us. You can see down here the different blocks, and you can make use this green area to leave comments, and that really helps us to, you know, hear what's going on
We'll also have some discussion and Q&A later in the session today, but this will really this is really another good way to communicate. So use the mural, and now we'll get back and move along to our presentation for today
And we're gonna be, as Matt said, talking about the CBTL, and we're gonna
Ask Lynn Warren, who's the leader of this project at Federal Highway, to share some background, and then we're going to be hearing from Nibs, who's working on a piece of this project, and from WSP that's working on
Another part of it. So Lynn, do you have some slides you want to use or you're just going to make a few opening remarks
Yeah, I don't have any slide. I'm just going to have a quick introduction to the projects and reserve time for the team. Thank you, Roger.
Alright, good afternoon, everyone. My name is Lynn Warren. I am with the FHWA Office of Bridges Instructors at headquarter in DC. Thank you for the opportunity allowed us to provide some update on the ongoing projects that our office sponsor the last few years
I will briefly introduce the projects. I want to save time for the research team, provide more detailed updates
So our office effort on centralized BIM transportation library or CBTL has been ongoing since 2020. The first project on project delivery workflow and a framework for CBTL was completed
In 2023, and the final report was published in 2024. From that work multiple bin based technical solution and artifact was identified
And a framework for CBTL was developed to manage these technical solutions.
In 2024 to further advance the effort on on this Cbtl concept. Our office funded 2 additional projects
One project is awarded to NIPS, led by Roger. The objective is to assess available resources and capabilities for ACBTL, validate the previous framework
and identify options to deploy CBTL.
The second project is awarded to WSB, led by Jack team conducting a pilot to demonstrate the creation
Use and management of CBTL.
So with that, I will hand it over to Nick's team to provide updates on the first project. I think after two team present, then we open up for discussion.
Yeah, thanks. Thanks, Lynn. Can you hear me? I'm sorry. I'm not sure what's happening to the screen share because I'm having a
Thank you.
computer issues so
Maybe Rakley, you can help out with sharing and getting Aaron to be the presenter so he can provide the nibs presentation.
Yeah, Aaron should be able to share his screen if he has slides.
You go.
Alright, pulling up now, I'm just
Peter's a little glitchy
If you have an issue, Aaron, it looks like my
Things are working, so I can potentially share the slides
Okay, I have it. If I have issues, I'm just going to cut my video out because this my work laptop is
Kind of shaky.
Hi
Yeah, we all work with computers, but that doesn't mean they don't give us challenges, right?
All right. Thank you all for having us. I'm excited to be able to speak with you on our work. So I'm Ericosta, associate professor at University of Florida, as well as a consultant with my own technical firm, S3 BIMTech
And so the kind of the team that we've been working with, you all know Roger and then Maynor from NIS is our technical staff, and then Monda could tell that many of you are already familiar with
And so how do we get here? Like Lynn mentioned, this has been going on for since 2020. They publish FHWA published the first report on the BIM for infrastructure
And then there are multiple states and federal grants such as the BIM pool funds and TPF, BIM for infrastructure. And then finally, there is a report in 2024 that kind of outlines what the CBTL is
And then that's how we got there, as well as what Lynn mentioned, there's two ongoing
Project right now, and we were working closely with WSP to make sure that we share our information and our alignment so we can tackle this whole concept together as a team.
So for our specific project objectives, we were tasked to assess the technical feasibilities about going into
You know, what a CBTL could be and what it should be, and so we really focused in on those aspects, right? For example, you know, how can we leverage current existing standards, such as BSDD, IFC 4.3? We looked at existing repository standards and DOT capabilities, and then mapped those into the technical architecture
requirements, and I'll share what that departments are next couple slides, evaluate and validate the technical requirements against real artifacts, repositories, and agency restraints that were previously published, whether from the previous reports or other DOT
artifacts. And then quickly assess the top BIM use cases that these BIM artifacts are in, and then score them against the validated technical requirements that we identified
Finally, with all this, we then developed a testing plan that this CBTL would have to go through, as well as a proof of concept plan of what would this look like, as well as a deployment plan for the metadata for harmonization and standards alignment through governments and national road
We previously published under NIBS document the citations there as well as we're focusing our next report to be under review for publication and hopefully next few months.
And so let's get back to what is a CBTA.
Well, essentially it's a living library at one centralized home for all the federated BIM artifacts that are already in use, right? So we listed a number of BIM types and BIM artifacts from the actual models or 3D cells to data dictionary, data management, MVDs, information manuals
Etc, etc. So everything needed for digital delivery or digital project delivery for the life cycle, at some point will be within one of these artifacts. And so we looked into the concept of why, or how can we leverage all these in one instead of
being siloed and, you know, disconnected, right? And so the goal of this is to be a unified platform of federated data, right? All these data lives somewhere and somehow. So how can we have a single source or a single landing page that can somehow integrate
all these… all these, so the people who need them can get freely access to them, be able to adopt them, use them, share them across freely, right? Because the end goal with all of this is for open standards, open data, so we can all share information accordingly.
And then likewise, there are some access control constraints, right? Because data is proprietary, data could be owned by the different states or agencies. And so there are access controls on each of these levels that go into
But again, the whole concept is to be able to share our data, right? So the community, the community feeds the library, and then the library feeds the community.
And so why now? Well, there's a lot of momentum building, right, with a lot of bid for bridges type work within a dot multiple grants going on, right? ASHO has created the J stand I can see over some of these governance, right? And the markets are ready, right?
BIM and digital delivery is coming, and it's already here for those states that aren't adopted, right? So a lot of several lead states that are already requiring different formats, digital delivery, the core technologies are already proven and exist
Right? And so the one core aspect that's missing is a shared centralized home that can help freely get this, share this across the different platforms.
And so why do we need it? Well, everybody who's dealt with BIM or proprietary information is we all live in silos. Digital data is scattered. It's farce. It could be damaged control. And so
There's a lot of issues today, right? And the ultimate result is wasted time, wasted money, and slower delivery. So without that shared foundation, every agency solves that same problem alone
So progress is fragmented, duplicated, installed
Alright, so what to pay us? There's a lot of games, right? With a platform like this, we're aiming for 100% open standards appliance, right? So the DOTs, the vendors, contractors can all ensure they get the correct information at the specific speed they need, right? So faster discovery, so you can increase the search time for specific assets or specific data models
A lot of reduce and rework. So there's no need for duplicate model creation. So the concepts like 3D models and cells, you can fundamentally create
reusable 3D 3D aspects that could be shared right? And likewise with the data, right? People can define data once it could be it could be utilized across different platforms, and that way there's no inconsistencies with what you're calling or what the semantics are for those terms.
Right? And important with this is the regulatory readiness, right? A lot of this involves the NISO standards. Most of you may have heard about 19650, about IFC and what BIM is. BIM level assignments, and so forth. And then what's most important, and one of
critical aspects that we look to is how are we going to be safe from both cybersecurity issues and intrusive
You know, malware and stuff. How can we ensure that our data is safe and secure, right? And so there's a lot of cybersecurity issues that and
methods to go ahead with with that
So
I know there's a lot of data we're showing here, but this chart kind of shows you the depth of detail that Tectum requires, right? This is in our upcoming report, but eventually we really looked into all aspects with all this, right? Each BIM artifact is different, and they have different requirements, they have different needs and different systems that need that
Right? And so we looked through each and every one of them, starting from the cloud, how we share it? What is security access need? How can we get to it via APIs and middleware? How do we control the artifacts? How do we do version controls, right? And then for the searching, can we do search? Can we use integration?
And what's really key about this, we looked into the AI and machine learning processes. Can we use these tools that are coming out to make sure we extract the correct data and get the ability to get these resources much quicker
Right? And so the quick preview of what this CBT architecture looks like. It's actually a combination approach because again, each artifact is different. A directory. So it's just like a landing page or a library that you go there and do a search, search for a different artifact, boom, get it.
Gateway approach. A lot of these data already stored elsewhere. We don't need to recreate the tools that already exist. So APIs give us access, such as VSDD. We can get into other format controls, and then finally, repository, there's… this is where we can actually house and host
These for for shared uses right? And so that's those are 3 implementation approaches that all have to be met within this hybrid approach. Security access model. Again, we use up-to-date OAuth 2.0 token based authorization that not only gives it to
the data, but the each agency or ownership of that data can set those requirements. And then finally, the data flow, for example, the BSDD, you know, how we can utilize ongoing and existing tools, such as BSDD, that can be pulled within the CVTL
And then to each state repositories, right? And so the previous matrix I showed determines which approach best serves that
Right? And so for the next
I think I'm going to hand this over to Roger or Mona
Yep. Thanks, Erin. So I know we only have a couple minutes today, so I'm going to give a very high level overview of the two areas that I've been leading on behalf of the team, which is the proof of concept plan and the deployment planning framework. Really, the proof of concept plan is really the bridge between the research we've done and actually putting the CBTL into practice. So we've spent really a lot of time understanding
The different types of VIM resources being created across the transportation agencies, where those resources live today and why we think they can be so difficult to find, access and understand, and even reuse. So the POC, proof of concept POC plan takes that research and turns it into a practical testing framework. So the idea is not to try to build the entire CBT all at once
It's iterative. It starts with a focused set of real use cases, representative artifacts, even actual users, and then we would test whether the concepts work the way we think they can. So questions that we're looking at really are, can people find the information they need across different systems
Can they understand what they're looking for, or looking at, and where it came from? Can we make information easier to discover without replacing the systems agencies that are already used? Does that CBTL actually make someone's work easier? I think that's the goal here across planning, design, construction, or even asset management
So those are the kinds of questions that the POC is really designed to answer. That's how we've written it. And importantly, it's not I think we need to distinguish that it's not a technical test. It's not only that. We're looking at the bigger ecosystem of how to make
The CBTL successful, so we're looking at user experience, metadata, governance, security, access, training, organizational development, and readiness even, and the different levels of digital maturity across agencies. So that would be the POC. The evidence, then it would feed directly into a deployment planning framework that we're currently designing. We're working through that right now, actually. So the deployment section is really about
Looking at what it would take to move from a successful proof of concept to something that can be adopted, supported, and sustained over time, because I think the reality is we can build a really amazing technical platform. It could technically function the way we want it to function
But still not achieve adoption, people won't use it, right? So what we're looking at here, my background is in change management, organizational development. I'm also a technologist, so it's a very interesting skill set. So that's the lens that I look at deployment planning from. I think there's a much larger ecosystem that really has to be considered. We've heard it the last couple days. It comes up consistently in our survey results with the DDSG overall. We also recognize that
ownership and governance around the CBTL matters, so there have to be processes for reviews, approvals, updating, even how we retire content. So agencies want to understand how the Cptl fits into their current systems and even their workflows.
What we're recommending as part of the deployment planning is training, communications, leadership support, technical assistance, time to adapt their processes, those survey questions, if you were part of our meeting yesterday, covered a lot of this, even though this is a CBTL
Some of those same challenges, I think, are consistent across all of digital delivery, including the CBTL. So for the deployment framework, we are trying to zoom out and look at that full picture, not just the technology and the data, but the government governance, the people process partnerships, resources
Consulting the consultant support, and even organizational support around it. So it's designed to help whichever organization ultimately assumes responsibility for the CBTL, to understand how they can move forward in phases. We don't have to really take this on
All at once. So, you'll see in the deployment plan when we publish, it really starts with targeted pilots, operational validation. It can expand through peer learning and early participation to broader state adoption, so it really is cyclical and phased in nature, and ultimately, hopefully, results in a more mature national
requirement where we can improve over time. The other thing I think is important to note before I close that we're intentionally not prescribing one fixed implementation schedule. There's freedom in the framework. It's really meant to give the future governing body a foundation that's practical, that can help make their decisions based on evidence
whatever available resources they have at the time, and really the readiness of the participating agencies. So, when you look at the work that will be published here soon, the proof of concept helps us determine whether and how the CBTL works. The deployment plan addresses what it's actually going to take to build it and make it successful and sustainable over time
Beyond the initial technology build. So, I know that that's a lot to cover in just a couple minutes, and we're still bringing all of this work together in the final report, so I'm looking forward to having more time in the future where we can have meetings and discussions around it to walk through the actual framework, the recommendations
And what it might mean for the broader transportation community.
Thanks, Simona. And thanks, Erin, for that overview of this project. As Lynn mentioned, you know, this is working alongside efforts that are currently underway to actually take what's outlined about how to approach it
Here and the proof of concept plan, and actually develop a proof of concept, and that's where we're going to go next, is to hear about that, and then once we hear about that from
WSP will have some chance to have some questions and discussion around
the approach. I will note, I put in the chat the link to the report that we did that laid out the technical aspects of a CBTL that Aaron briefly summarized, but there's a lot more detail in there
That you'll be interested in. So, yeah, and hopefully we'll be doing more on this at the next DDSG meeting, but just wanted to give a quick overview of the work we've been doing, and now Jag's going to take over for WSP and show us
how proof of concept is coming together following these outlines, which were originally this effort was started in research that JAG and WSP did. So I'm sure you'll be talking a little bit about that Jag, but
Are you able to share your screen and
Trying to share the screen, so let's see
Are you able to see what I'm sharing?
We can see that. Yeah
Okay, let me put it in presentation mode
Okay
There we go
So, yeah, thank you, first of all, I mean it's great we're able to speak about CBTL after several years of ideation. Thank you for that introduction, Erin and Mona and Roger and Lyn
Gag, you're gonna… you're gonna have to swap your
We're seeing your speaker note version.
Oh, okay, let me see, I don't need the speaker notes
Let's see
How do I get rid of that
Let me see
I think you go to the three dots and then it will give you the option, Jeff.
Three dots
Maybe it is connected to a different
Yeah.
You have two screens, Jack, it might be on your other screen. So you've pointed to screen one, but you want
Hmm
point to the other screen. If you maybe stop sharing and then reshare and
Okay.
share your other screen that might do it, because that's where the
One of them opens up on one screen
Can you hear me now?
Don't we hear you just fine. We're not seeing anything yet
Okay, all right, let me see. I have no idea what's going on it's
Talking on and off, so I apologize
You found the share button. Which screen you want to share
Right.
And if you have two screens, it'll show one and two. And when you use presentation mode PowerPoint, it will put
presentation on your
screen where you have PowerPoint sitting, and it'll open the
I see. Okay, let me
Let me try this one
And let's see
Still seeing them minimized version
Still seeing the minimized version? Okay
Or maybe if you hit presentation down there on PowerPoint, what does that do?
I'm seeing the full screen, but
Yeah, do you have two monitors?
Yes, I do, so that's probably
We're still waiting.
If you go to Display Settings at the top there
Yeah.
Swap
swap presenter view and slideshow.
There we go. Okay, perfect. Now, is it good?
Yes, now we got it
All right, well, thank you. I appreciate it. I don't work with multiple screens usually in the office, so I think… Okay, I appreciate it. We'll make up for the time. Thanks for all those introductions. Yes, this has been a long running project, so let me get into it
It's called a central BIM Transportation library. I think the concept was originally developed as was mentioned in our original research that Lynn on the BIM workflows project, and it was one of the chapters there
And that concept was proposed
In that project and then Roger and team and Aaron picked it up and did some more research on it and presented
Some of the requirements for it. So this project which started simultaneously
With Rogers project on looking at the requirements
Was really to bring to life and showcase, you know, what
SCBTL will look like
in real life, you know, this concept when it started was probably ahead of its time, but
I think as Aaron said, I think things are coming together now. And what is coming together? We have
And IDM, we have an IDS, we have a data dictionary from the BIM for Bridges portfolio that has been used actually on projects.
We have just about finished the internal version of an IDS for the roadway or the infrastructure side
So these artifacts
Hit the street and start getting specified in real world projects
And
As we change these dictionaries or we expand them, or add elements to them
Or change our specification because we have a new use case and new requirements
There will be a new version of everything that we created today.
And that is going to happen
forever, you know, going forward, as we refine, learn more, adapt, you know, and expand how we can deliver projects digitally, more use cases will come on, more needs will come to the surface
And better specifications might come in, better formats even might come in.
As the system evolves, the basis for this project was that we knew or we can already envision that there will be confusion if we don't have a consistent way of taking the nationally created standards
and referencing them in projects, you know, with proper version control, and you can easily relate to it with various, let's say, authoring software versions.
So the CBTL concept was supposed to
In this proof of concept, I think you just heard the proof of concept plan. It is a proof of concept, or a prototype of an instance of some of those artifacts being managed
By people and governed in a proper way to ensure proper versioning
And then provide it from a repository, at least the national standards that then can connect to state extensions and then be used in
Authoring data in native software and validation
So it connects a lot of things. So what I'm going to present today is the concept
Which we have a sprint from now to May of next year, end of May. We have a 12-month run to build the prototype
And showcase its value, so that's essentially the presentation for today.
So, but I'll take a little bit of a step back, you know, before launching into it. There are three columns here. I'll go left to right on this one
You know.
Digital delivery is more about people and
That is the foundation of governance is essentially a people and process thing. Certainly digital delivery can only succeed when governance of open standards is led in a coordinated way and thanks to AASHTO, Federal Highway, state DOT
There is coalescing of forces to create that body to govern these standards as they're appearing, right? But it has to be supported by clear process rules and decision structures
You know, there should be a process for standards creation and approval, and then stewardship and oversight of those
And then aligning all the people or all the agencies that are involved in the creation and all the committees responsible for approvals, and all the stakeholders that will use it
getting them to align with each other is essential before we can, before the technology set that we're creating, in this case digital standards can achieve scale and use.
So, one part, I think the most important part is people and process. And this presentation obviously is only touching it because it is recognized as a very important piece
There is already a lot of movement on trying to get the digital standards under control as the pool funds are creating them, as the AASHTO bodies are approving them, and, you know, as they're getting published
So that's one piece. The second piece of that is once a digital standard is approved
You need technology, as I mentioned, to
Make sure it's provisioned, you know, and then implemented in projects in a uniform way, so we are not passing it on spreadsheets or files that we can have a place where we can go and, you know, grab information, you know, and
you know, use that information. So
So we have that piece as well. So that technology piece is essentially the CBTL. In this case, in this prototype, we are saying that we can help implement those national standards
and processes and create an architecture to serve those standards
And what are we serving? In this example, we will talk about the BIM artifacts that we are looking at our data dictionaries. Starting with exchange information requirements
For the specific exchanges we're interested in, that is being worked on today.
the data dictionaries, the information delivery manuals that are connected to those, use cases in the exchanges, as well as the specifications that software will use to build and validate that the data that's being created in native authoring
software is actually interoperable, the mapping to IFC, for example. So, it helps apply those national data dictionaries and classifications consistently across project workflows and makes governance of these national standards real by providing a platform
for the governance on the left hand side, the people and their processes to actually have a tool to be able to govern those national artifacts. So
A lot of this has… we don't have to solve, this is not a greenfield problem
The Europeans have already looked at a lot of these things and just drawing inspiration from them, there is sense structures, the governing bodies for the standards, there is a people-side governance
In Europe, there is also a data act and there is technical standards that they are using to
put in place both the people process and they are working on the technology solutions, you know, to be able to govern those digital standards. So, essentially, that's kind of the setup for
You know, for this particular project.
In our prototype, in this proof of concept
C V T the CVTL will manage, it can do more than what we are
proposing today. As Aaron said, there are many ways the CBTL can be used, and many more uses for it, but in this case, we are managing and governing, essentially, the BIM artifacts, classifications
objects, their dictionaries, AIRs, IDSs, IDMs
any process models have been execution plans. I mean, it is set up to do all of that. It will host the national and state BIM artifacts together in one
governed environment if you choose to do so, but as a minimum, it will host national artifacts. The solution that I'll show you is meant for multi-tenancy. In other words, states can use the same architecture to post their BIM artifacts or extensions of national standards if they choose to
Use any, which I'm sure every state will extend it to their need, or they can connect into the national standard, you know, so it can host those, and the core value here is that we're aligning and making sure that the versions are kept tight
And we have a tool to govern those national standards and version them so that people can actually use them and specify the correct version, you know, in their work.
So
As far as the scope of this POC, our pilot is concerned, we will aspire to acquire, create and ingest approved PIM artifacts onto the platform just to show as examples. For example, the pool fund
created artifacts for data dictionaries, EIRS and IDM IDS
We'll establish and demonstrate the CPTL content management and governance workflows, how it actually
you know, happens in real life. Certainly as we do this, we want to engage in all of you in DDSG and others, national and state agency stakeholders to test
The project you usage workflows of the CPTL content so that you can touch and feel what we're talking about in terms of the technology solution, the CBTL is that technology solution that helps people to manage and govern their processes. So that is
Really, the objective of this project. I'll walk through maybe how the prototype will fit together. Sorry, this animation API shows up first, but, it is API-based, but
Basically, in this slide, I'll show how the CBTL prototype fits together as one governed platform, building it layer by layer as I animate this. So on each click you'll see a new part of it. So the first thing is who uses it
User roles
To manage the, as I said, the central purpose of the pilot that we're doing, a POC is to manage national artifacts approved
Standards, you know, so we start with that in mind, so
there is some governance structure that needs to come together. I know that work is ongoing in that, and it's not yet settled on what that governance structure is, or who will take… who will take leadership in governing the nationally approved digital standards
But we'll have 1, you know, before too long, you know, JSTEN, for example, is one. Federal Highway has a role in it, you know, maybe there is a national standard steering committee that comes together, maybe others, but that's beyond my pay grade on this call
But there is, there will be somebody, you know, who is in charge of saying, yes, this is the authoritative standard. So the content is not owned by the platform, it's stewarded by the community and placed in the platform. So this is the people and process side that keeps the standards authoritative. So whatever enters
Here, you know essentially is, you know is that standard that has already been approved. So there is a governance structure
The governance structure has roles. You know, clearly there is an administrative role for people that will sanction, you know, or approve
Artifacts we placed here. There is roles for state DOTs to critique or maybe have edit rights
There is a role for technology providers, consultants, contractors, and general public, potentially to read, search, and discover what's in the CVTL, as I think Aaron mentioned. So there are roles for administrators who can actually edit and potentially some state body or a grouping of ASHTO bodies come together for that
State duties may raise changes, you know, they may have a special privilege or access. And then a large majority of people can at least see what's in the platform so they understand what objects exist, what the exchange information requirements look like, what the versions look like, how things have changed over time
You know, so there is a role-based access control, and that's the central point of this
In terms of the core platform capabilities, so we know we have user management in RBAC, role-based access control
There is artifact repositories, so we'll create some sort of repository for all the artifacts that need to live inside it.
You know, the back end of this could be what is called as GitHub as a repo, or some other, you know, database technology that can keep track of version control. Maybe it's done at the database level or object level. We can decide what's done, but there's some repository for artifacts like the EIR
RDMs and IDS is national content, data dictionaries, there could be data templates and guidance. There is certainly one of the core features of this is that we should have version and change management control
There is a dictionary management that needs to… I think we have to have some sort of a dictionary management, capability because
Right now, our dictionary is both on both pool funds are in Excel spreadsheets and certainly
And that's not tenable for proper dictionary management. So we need to be able to
ingest those Excels or any other format that it comes in, normalize the data against the semantics and classifications, and allow people to browse, search, and edit what's in the dictionary, and then link the dictionary content, you know, using existing mappings, or maybe new mappings to BSDD, for example, the data dictionary service of the Building Smart International for the IFC
Or any other dictionary service, you know, whatever is in our content should be able to be mapped to international content. You know, some of that mapping is already happening in the pool funds, but mappings can also be taking place with other services, dictionary services that we can map to
And it links, you know, all the artifacts in there. And then the last feature there is standards integration
which is normalizing the data, ability to browse and search, you know, there should be some sort of an integration with international standards, and the final part piece is the Knowledge Hub
You know, which is your chatbot style in a knowledge hub that, you know gives you a quick overview of what's there, you know maybe gives you guidance on how to use it, you know, potentially training and FAQs and others. So essentially, we can create a knowledge hub that sits in the platform. So these are some of
In a core platform capabilities that we're envisioning, we'll see how far we can go with the prototype. So we know there is RBAC control. We know it has content in it coming from the national standards.
Then we build API-based services to expose that content. The API web services, you know, there'll be a gateway to authenticate access
And the capabilities of the web services will be… we'll be able to search the metadata. You should be able to query, you should be able to
You know, use webhooks to actually connect the data. So, basically, the gateway controls access
and provides all the data that's inside the platform through a set of API-based web services. This is how we communicate information. So if the project specification is seeking a certain version of a national standard, it should be able to connect into the content pull down
using the API web services and programmers should be able to write that very easily. Okay, so that is… these are the top three layers in very core to the CBTL. Now, the content you know where does it come from? It comes from the pool fund studies
You know, certainly the BSDD data dictionary, this is a dictionary service. Linking comes from BSDD, OGC standards. We can place other national standards, FHWA, Meyer, HPMS, and NBI, any national standard that needs to be in the content library we can place. So it works not just for what's happening in digital delivery, but also for other standards.
Certainly there is security, identity access management. That's part of the RBAC controls. Another feature I don't think we'll be able to build this out completely, but it's a core feature of this is that we would have
This repository or this platform is a multi-tenant platform. In other words, we'd have national content in one part of the
platform, but in other parts, you know, we can partition it to include state DOT environments. Let's say if a state does not have an ability to manage their data dictionaries
Or IDMs and IDSs on their own, they can… will have partitions in there for multiple tenants, you know, to be able to occupy the same space and pull down the same architecture and API abilities to connect to first of all, host their data, govern it
And then link it to the national standard if they wish to. Now, there may be states, and we'll hear from one later today, Caltrans
We may not need this multi-tenancy. They may not need to bring in their data into our platform to be able to connect to the national. They have their own digital product catalog
information framework that is also an API-based service, so we can connect anything that's external also into the CBTL. The idea is to align, you know.
your state standards using the API gateway and the CBTL gateway that is being built here to the national standards. So without that, everybody can have their information framework, but there is no central point to access whether that framework and information content
aligns with the national standards, so this makes that easier to do
So those are the core features of the platform. So in terms of our prototype, either when we finish this, we want to demonstrate
this platform, and show how BIM standards that are being created at the national level, like the data dictionaries and IDMs and IDSs
Can be managed and essentially we'll place content, you know, we'll give roles and access to people. If somebody wants to suggest a change, you know, we'll show how that change can be raised and how we can actually edit the content and version it and make it available. So that's kind of the demo. You know, we are hoping that the outcome essentially
Make the technology piece come to life. Once we solve the people and governance piece and the technology will be there to ready to go.
So, I will take a couple more slides just showcase, you know, how the workflows might happen. You know, these are example workflows, these are all potentially the proofs that we will do as we roll this project, too. Our first job is to actually build
The tool and the platform and the API process, and then we will initiate as we engage with the industry, with all of you, you know, on, you know what workflows we'll prioritize. But in our mind, as far as our plan is concerned, we'll definitely
A workflow that will ingest a pool fund standard and publish that standard to BSDD
You know, for example, U.S. standards are built in the US
Our data dictionaries and IDMs and IDSs are built here. Once they're approved, they can go into the CBTL, and CBTL essentially is a dictionary service that says, here is my dictionary
And here's the API that exposes my dictionary. Now, we can push that to BSDD
As US standard or to any other dictionary service. So, that will be one workflow where we ingest the standard
Govern and approve that standard using the governance framework and publish to a CBT or repository and push that to an external data dictionary. So that'll be an awesome way to say, you know, we don't place everything first into an external service. We have our own dictionary service essentially
that we govern through the people and process that we have in place. The second workflow is to manage changes to published content. You know, we'll raise a change proposal, we'll demonstrate the use of all of these in the examples. That's our hope.
If we request a change against, let's say, an EIR or data dictionary item or an IDS,
capture the national landscape in a review and assess the impact of the change, you know, so again, that's the people side of things. But we should be able to raise a change, so somebody with the right role in the governance structure should propose, or it could be a state DOT that can come in and say
Here's a change we are proposing. Maybe another state says the same thing, maybe 5 states have 5 different changes, and if you examine them, three of them are the same. So, in which case, the governance body says, yeah, I think we should add this item, and we should push it to the IDM. You know, if you want to do that, we can do that
You know, review and assess the impact
You know, if that changes are approved by the governance body, we update the EIR data dictionary in IDS, and then republish and re-sync the data dictionary service to external entities. So… so we'll not only show a workflow where we can ingest and publish
Through APIs, but we'll also show a workflow where we make a change and republish and resync. So these are
important governance mechanisms for the national repository. Now, we hope that real proof in pudding will be
Really, when we actually make the workflows come to life on projects where
a project actually pulls down a national requirement, so this is a workflow that shows from national content a validated project IFC data. So let's say there is a project in DOT X, you know, they
have a requirement in that project, you know, to use a specified EIR that's in the National Dictionary
In the CBTL with its associated data dictionary IDM and IDS
The idea is that the project should be able to say, I want to hit the national content to pull down the correct version of the
IDM that I want to use, and EIR that I want to use
From that, I want to add my own state extensions. Maybe I want some more objects, you know if needed. Again, that's not mandatory
You can simply layer on the state-specific requirements to the national, so that we are still aligned with the national content, but you're essentially adding your own requirements
What this does is you have… you're not forking the national content, you're not doing your own state thing, you're always aligned and anchored as a minimum viable product to the national content, and you're adding your own requirements
You create a data template based on the EIR and the data dictionary. That's
both national plus state if needed. And then you send that to the authoring tool, any authoring tool to create
The data, the then you model, you author your model externally, not in the CPTL.
The model exports the IFC. Now, you may have an IFC validation service
Either built into the platform, not necessary. There is an IFC validation pool fund happening. Let's say the validation service says I'm going to always check your IFC file against the national requirement
You can have that service run because you have exported to the IFC. The data dictionary and the related content, the rules for checking that are already existent because the CBTL has the authoritative information. You check your IFC against the project's governing ideas
And the National CBTL version plus any state extension and you document findings, whether that passed or failed. So in this way, a project workflow is correctly referencing the correct version of your EIR and related DD and IDM IDS
You're also being able to check whether you're producing the right files
Per these national standards that you're referencing in your projects. So, it's a very powerful workflow that the CBTL can make happen at the project level.
None of those services, validation service
Authoring doesn't happen inside the CPTL. CBTL is simply providing the national content against which you check your files. Okay, so that's the workflow that's envisioned here. So hopefully that gives you an idea of how this
comes to life.
We have a very, very aggressive work plan. That's why we are heads down right now in trying to first of all, build that portal and the interface. We have requirements document done
We're in, we have multiple modules that dictionary management system, the cloud architecture for versioning and integration
The project delivery tool development, you know, this workflow engine and then
The information requirements and interoperability management module. So all of these are artifacts. And then once we have enough build out
Of the platform done, we will start, you know, taking some of the national content and placing it in, and inviting all of you to view the demonstrations, critique them, and document, you know, what changes may be needed. But the plan is to get the platform up and running
Get some content placed using what is already available nationally and showcase how a CBTL really helps us govern the national standards and how it can hopefully by the end of the project also showcase how project specification can then relate to a national standard at a state DOT.
And then use it in that way. So, that's kind of… it's very aggressive pathway. I think we can build this very quickly, and do a quick demonstration of some of what the CBTL is intended to be. There are many, many, as I said
Things that CVTL in general can do and I think Aaron pointed to many of those, but this one is specifically focused and built on managing the national artifacts and using them at the project level.
That's all I have to share, but I'll say one thing. I'm sorry you have to leave at 2:15, but I was keen to hear the DPC. Of course, I talked to Caltrans quite a bit and I've been following what they have been doing for three years or two and a half years now
I believe that Caltrans has its own information framework, and I think it can really
You know, when they have their data in their framework, it can connect through their API services to the CPTL. And if all 50 states do that and pull down the national artifacts, then we'll be in complete alignment, at least with the MVP that's in the National Consensus Requirements
So I'll stop there, Roger. I hope I didn't run over time
No, that's good. Thanks, Jag. We're doing fine. Thank you for that deep dive into what's, well, not super deep, but you got into what you're actually doing and how it's going to work. So that was nice to see
and continue to learn about. It looks like we do have a few questions. We could take a couple of questions
Before we move on to hear from Caltrans, maybe if there's questions about some of the things that you presented, and then we could hear from Caltrans and then talk a little bit more about
Dictionary in total
or the dictionary, the CBTL concept library dictionaries in total
Let's see, does anybody
Have a question I want to ask Jag.
There is a this comment from Tricia and looking at the chat, Roger, if you want me to take notes.
Yeah, yeah, go ahead, Jake. Yeah
So, I think Tricia, your question about does the tool have the ability? So as we're building out this platform, I think one of the things that we do want is
that there is a formal process for raising changes, which is, you know, certainly, you know, there's a formal process to raise a change. I think that if states start using this, and we have… we will have a formal mechanism to raise a change. Let's say you add a data dictionary, a new object to the data dictionary.
That is the formal part, so it will definitely have that, but there is also a community board that we can develop, you know, I'm not sure how far we get into the POC
You know where people can leave discussions, and unmoderated boards, I'm not a huge fan of, Trisha, but there will be an informal, you know, component in the knowledge hub where people… there is a portal, you know, like a Yammer site or something, where people can put in comments, but I think the key is monitoring and making sure that feedback comes
But there is a formal portion
for capturing feedback, you know, and change requests, and then there is this informal process. So I think it can have… these are the requirements that we need to capture, Trisha, so I think you're raising an important point there, and that's been envisioned, not completely designed yet, okay?
Definitely can be.
Thank you.
Sure.
Anthony
Okay, Anthony had a question, Roger, if you want me to just go down the list. I think doesn't facilitating multiple libraries that is national standard versus Caltrans defeat the purpose? I think Jeff answered this very well
I think just like IFC doesn't serve all of what we need, at the international level
I don't believe in national standards as we're building it, we already know that we're coming up with consensus set of properties.
Right, that worked for all.
But I envision, I think maybe, Jeff, that's what you're alluding to here is there is a minimum consensus set. That is our national standard
We as we have an obligation to get behind that national standard, I think, in all the 50 states. Otherwise, there is no movement on the software industry
But beyond that, there will be state-specific things that you want to add, things that will never get into that consensus
So I don't think it defeats the purpose. I believe it strengthens the purpose that we are all getting behind, let's say, 70% of what we need, and layering on 30%, in my view. So I think I am in agreement with what Jeff is saying. Without paraphrasing him too much here.
If that makes sense. So
Let's it, I think Aaron also answered some of that. Rick, Rick Bryce said can you expand on how the CBTL will generate a native model authoring template? Okay, so CBTL will not generate the data templating is a very, very interesting concept, Rick. I think this is one of the reasons, one of the
Strengths of, I think having aspiring to a national minimum set of standards
Let's say at a project level, let's say you don't have any state layering. Let's say you have, you want to follow the EIR
As it's defined in the BIM for bridges and structures pool fund for design to construction model exchange.
you know, you would have a set of, you know the EIR will already comes with its own
You know, data dictionary content, either the use cases that it articulates, the
And the IDS. Using that you can create
A set of requirements that essentially are a data template for the authoring tool to say, this is what I need to produce
You know where in the authoring tool do I need to put the data in? So essentially the data template concept is why we have in a standardization here in the first place. I think
I hope that as we get through this project, we can demonstrate that in a simple level, to say that if you're aligned with a national exchange information requirement, you're already aligned with what data you need, and therefore you can create a template that the authoring tools can consume and build against to make sure that data exists
I don't see any more here, Roger. I hope I answered all of those.
We can have a workshop and I hope you know your September date, I am able to make it but I think
Having your hands on, you won't get the hands-on until we finish building the platform, but I think at some point, we should have these questions answered with real examples.
Anyway, I think what could be interesting in workshop might be if those are the workflows that you're planning to support with this proof of concept
Could we get some discussion around
What… how people see those actually happening and what they might need or not need to support them if you're going to do that. And I think the other thing could be interesting are those workflows compared to the BIM uses… to the use cases that
We're originally identified, and where are we aligning with those? Are we covering multiples of those? Are there others that
Some might see as high high priority requirements compared to the four
Workflows that you identified, Jack
Yeah, I think 100% right. I think I'll go back to Rick's comment about and your comment about use case. So let's say there is an EIR, the EIR is tied to four use cases in the national
Let's say they have 4 use cases we want within the EIR. Let's say design to construction. We want to… we want to send the model, the 3D model, we want to send pay items, you know, we want to send AMG files, whatever the case is. Let's say those are the… those are in the national
The way the data templating will work is at a state level, I don't want to pay items
You know, Mark is on Mark may say, I'm going to toggle off this use case. I only am interested in AMG files and sending my model to construction. He should be able to click, click.
And pick from the list of use cases, and then that should tell him what elements of the data dictionary and are valid and what objects get included in what p sets and properties get included and what the IDS looks like for those.
So that is essentially your data template. So I think having that conversation and a live demo would be, I think your point is very good. We should workshop… I'm not set on the minimum viable product for this project is the national content hosting and version change. You know, that will be
AASHTO, National Stadium Committee. It's a tool for them, right? That is my number one goal. Our number two goal is really to create the project workflows, because I believe that's where the real value is. But I think we should workshop this to get more requirements in. Oh, this would be nice to have it with some concrete examples
Yeah.
That would be a great idea for a workshop. Yeah
That could be a good thing. And if any any of the
people that are joining us today are interested in sharing what they're doing. We have Caltrans here, and we'll hear from Mark and Devin here in just a minute, but it'd be interesting to hear if other states are developing
Dictionaries or repositories that they think could be shared and would benefit from that. That could be part of this workshop that we might be doing in September. So if you do feel that, if you do think you might be interested.
Yeah, if you can drop us a note in the chat or in the mural, that would be great. We did hear back in January from
Rick's here, but from Washington dot about their work with signs and how they're making up a database of signage. You know, that seems like a kind of thing that would benefit from this
Ability to share and store and share in a consistent way. So that could be interesting to revisit.
So
We'll keep after that, but maybe a good time now to let Mark and Devin take over, share with us about what they're doing with their project, and then we'll come back after that and have a few more discussions. We got a few poll questions, I think
We got that started, but we'll come back to that after we hear from Mark and Devin. So Devin, Mark, take it away. Thank you.
Thanks, Roger. And yeah, no, I like the questions and the conversation. I think some of what Mark and I are going to share is maybe even going to help touch on some of that of
Why you would have a state-specific part as well as a national part. So first, just start with some introductions, you know, for those that don't know me, my name is Devin Poor. I'm the BIM for Infrastructure Program Director here at Caltrans, and I'm joined with
My buddy Mark over in surveys. Mark, go ahead.
Sure. Yep. Deputy Division Chief of the Office of Land Surveys with the Division of Right away and land surveys.
Thank you. So yeah, we're here today to share what we've accomplished to this point with our digital products catalog effort. This started early on, one of the first ADCMS grants
In order for us to achieve our ultimate goal of BIM for infrastructure, where it's more than just enabling the design to construction, but really tying in how does this information get connected to the assets and that lifecycle picture
So we submitted a grant concept and with FHWA, you know, got approval of developing that 1st tool
As far as we know in dot's that can help establish, you know, a better information framework that is going to help connect our people, standards, workflows, and data across project delivery and beyond that. So, you know, the whole focus of it really is digitizing, centralizing our standards. You know, we all know that we've got certain standards in certain places. Sometimes they're not digital
And regardless, if they're not centralized, they're still siloed. So, you know, siloed standards, digital or not, is still siloed data. So our big focus with this is, you know, how do we better understand not just what we need in design, not just what we need in construction, but how do we connect that
Information beyond how do we connect design and construction better? How do we, you know, enable what information is needed in maintenance and operations during design and not putting that on construction to just figure out the asset information. How can you know how can we just better
organize that information, have, you know better federation to all of our information. So
I'm going to turn it over to Mark here to take on the rest of it, unless there's anything else you want to add to this slide, Mark.
No, I'll pick it up from here. Thanks, Devin.
And thanks everyone for your attention today. So a few of us, we did a trip a few years back and we're over in Europe, and it was interesting, a country that will remain unnamed because they've done a lot of amazing work in the world, the space of BIM with transportation, but
We basically were able to see under the hood of both their Their Department of Transportation, and then also their Department of Rail. And so what we saw was we saw 2 amazing
been the charity models coming out of 2 different groups working for the same government. But the one thing that we that we saw, this is probably the first time I think we really got tipped off to this was
As we are listening and looking and experiencing their data dictionaries, their BIM libraries, their standards
It just hit us
I don't think they talk to each other
Right? And and so I… I had to be the one to ask the question, and I asked the rail, and I asked the Department of Transportation, hey, you know, everything looks amazing.
But it doesn't sound like you're doing it together. And they basically confirmed, right? And they said, you know.
Over the last 10 years, we just… we've been working in parallel to each other, but we're not really doing any sort of collaboration with each other.
So that really hit us hard because in California, quite a bit of people here, different organizations look up to us and look to us for leadership and guidance when it comes to digital delivery.
So we brought that back and then also considering the big pie in the sky dream where all the different DOTs can work together. You know, there's just… it was like a sort of like a tree branch of a problem to solve. So
We just continually found ourselves, like, we need to build a digital hub.
There's just no way around this. If we want to be in a place where we're able to share information, not just within ourselves, but whether it's with other agencies, state agencies, like our Department of Water Resources, CalHR, I guess we could do them too, but Highway Pat
I was thinking at CalH or even outside of that, right? Locals, counties, cities, things of that nature. We realized we had we had almost like a field of dreams at the at the risk of sounding very cliche, we had to build it before they could come. And so what you're going to see today is our our first phase of building a digital home for digital standards
Because what we learned in Europe was siloed standards produces siloed data
Those two different agencies in that country could share data.
They could do really awesome work apart from each other, but they couldn't bring that data together.
So, so I think if you get… if anyone gets anything out of this, just silo standards produce siloed data.
And I think Aaron and Jag, I think Mona did a great job touching on a lot of these problems and some of the possible solutions. Okay, Devin, watch me on the clock to just make sure you can give me one of these, right? But that sets up the problem statement
And yeah, so the idea is, you know, okay, so that was problem number one. We need to build a home. I'm going to show you the home in a little bit, but then the next thing was, okay, well, do we want to do… just have a home for the standards, or can we do something with it? And phase one was developing processes using those centralized and digitized standards
to produce template products for ourselves. I'll show you a little bit about that. Then after that, it's like, well, what can we do with those standards outside of template production? So we started to create ETL tools. You know, one of the first extract, transform, and load tools that we created using FME Server was
to be able to take data from one proprietary drawing container and convert that into another proprietary drawing container.
And then the concept of having better connected outcomes, right? How… how do we better connect ourselves with a project delivery within our own program? And then how can we then leverage this home, this digital home, to connect ops and maintenance, asset management, division of Finance
Because that's where asset management lives for us, and a myriad of other programs that are all within the 22,000 canopy of Caltrans.
Okay, so I'm going to just bring the DPC product over so you can take a quick look. We're going to look at the existing catalog. I'm not going to take you through all these, but you can add new products to the catalog. You can subtract or retire these products.
And then some of the main template products we create are featured co-libraries. That's what we use in the field to build stuff or inspect assets. Then we also can create workspace XML configuration files. And these are all things we're doing now on the daily. This is just part of this is now becoming status quo, right, Devin? And that was the goal from the beginning
to go from, oh my gosh, how are we going to do this to, hey, this is just how we do work. This is, like, every day. And then the JSON file, so that way we can support that GIS migration and sharing of information within Civil 3D ArcGIS Pro TBC in Mach 9.
All right, so
Let's get over here and bring this up.
So for Trish, she's probably seen this too many times. The interface itself is still very much looking the same, but what we've been doing is doing a lot of back-end work to support 19650 and that'll be phase two. I'm going to get to that after this little demo
As we go through this, you can see there's many different types or groupings for our assets. And the reason why we've done that is because different groups within project delivery at this point are looking for different experiences with those same assets, as I'm sure everybody's well aware
But something as simple as, let's just go to say traffic control
And this is where something like a digital products catalog is going to be extremely helpful for any dot that's looking to do BIM for I say something as simple as a sign. That's a sign line. You want a sign post
Okay, so say something as simple as a sign. When you go through a sign
Here in the Feature Code Library, this is going to be for your polymer design surveys.
It shows up as just a single asset. But my friends, I know my friends at Oregon and Washington, we've already went over this. We all know that depending on which program you're working for, a sign can be more than one asset, correct? It can be a base, the base in and of itself can be its own asset with its own tag ID
Trish knows this very well. It could be the placard right? And so right out the gate, you can see that we already have an issue of having siloed data, because you've got one group in one program interacting with the asset as a single entity. Then you have another group
working with the same asset, but as a sort of multi-component family tree, right? You got the parent, and you've got the different children. And so, what we're… what we're now in the process of doing is
taking that level of complexity that we're going to need to basically branch out and
Building the DPC backend to fully support the 19650 paradigm or vision or dream, whatever you want to call it.
So this way, now moving forward, once we get through second phase, we'll be able to click on any asset
And select any program and then be able to see which template user needs what creates what consumes what or has authority over what. All the way through the lifecycle asset. And we'll know what's driving those decisions or behaviors. That's the organizational information requirements
And then your asset information requirements, your Pirs, your projects, and then we'll know how to exchange everything. So all of this is going to be contained in the Dbc. So it could be as simple as Devin going in one day and saying, Hey, I wonder what asset management does with a signed pedestal
At the phase of retirement. And they should be able to click on that asset, drill down, and it'll say exactly who owns what, who creates what, who consumes what for that asset at that point of the life cycle.
And then you might be asking yourself, well, you know Mark, what's sort of the point of all this? It's just like, is that just like a glorified sort of catalog? It could be, if that's where you stop, but that's not where we stop. So, right here, these are our template generators
And what that means is, I'll just show you one real quick. So I can basically come over here. I can grab the type of template I want to create. I'm going to create an Fxl. That's for the Trimble domain Trimble ecosystem. I can pick which domain I want. So say
Say I'm doing something for asset management, and they're maybe using Trimble Unity Maintain or something. So now I can collect asset management. If I want, I can make it unique to that particular contract that they're working on, or if it's not unique to contracts, just leave it open
Then I can pick the category that I'm looking for. Maybe they're an inspection. Now, when I click export, what it's going to do is it's going to take all the mapping that we've already preloaded for asset management doing its routine inspection. It's going to create the feature code library just for
And then once you have that all set up, you say, well, Mark, I like to do GIS. Hey, so do we. And then you can come right over to here and then you can get into your GIS. And then you can get into your Civil 3D and all this stuff just exports on the fly
Right? If I were to make an update here on any of the assets, we have an approval process, and then it goes from staging to production databases, and then once that's published
Anybody that's creating any sort of downstream templates that we've already pre-configured, they're going to get all those updates. So the idea is you update it once, and you get many expressions.
The last thing I want to show, this is our… what's called our simple 3D DGN converter. Now, because we've got everything digitized and centralized, we can do
And this is low-hanging fruit. The hard part is getting everything in there. At least that's the woodchopping part. Now, once we have this, all I have to do is drag and drop a DWG. That's a simple 3D drawing right here. I pick my scale, I can send emails to anybody on the product delivery team
And then I hit run. And then, while this is running on the side, on the second monitor, I can still be working in my simple 3D environment once the conversion is done, everybody that's on the email thread gets pinged. Hey, your DGN's ready. You go and download it. So those are just two examples of things you can do once you centralize
digitized and centralize your standards.
Okay, so moving on
Now that we're really embracing this information framework mindset where we've recognized we're going to have to build a bigger field. That's one thing, Devin, about field of dreams. They assume that that size field was going to be good forever, right? That's the happy end ever after kind of thing
But what field of genes didn't touch on is the reality that, you know, sometimes you got to start it at little league stadium and kind of go up to your high school stadium, then you got to sort of phase it out and build it out until you actually got your your Wrigley field. We're not at Wrigley Field yet, but we're well on our way
So moving on. So now that we've got, say, like our little league stadium built, now we actually need people to play ball, right? The field's built, we're ready to rock and roll.
And so we've got two… basically, our approach is what we're calling the Caltrans Information Framework Team. And right now, Devin, how many people do we got right now in the IFT?
I think it's like 45.
Okay. And is it just project delivery?
No, no, we've got our partners from outside of Project Delivery that are now joining us
And that's one of the things I think we're most proud of right now is we do have many different representatives from operations and maintenance, from data governance, from enterprise GIS, asset management, traffic operations.
We're starting to really build this team of experts and we're training them and raising them up to use the digital home that we've created for them. And the idea is we're now at this point of convergence where our staff, our team, as well as the digital home are now going to evolve and grow together.
But now at this point of convergence where they come together and we all grow and build out together. So we'll have some sort of permanent governance team in place at the headquarters level, and then… and this is where we're at right now, is building this team. And then the IFT working groups, those are the working groups that'll basically spread across the state
All reporting up into this governance team.
But there's still a lot of things we haven't figured out. We're well in the very… the infant stage of putting all this together.
And so to summarize, standards first, right? Centralized once, put it to work.
everywhere, right? And this is where you get your dividends. So we've we've digitized and centralized certain portions of our standards. and we're using that to do special projects, middle mile broadband, right? We've got a ton of contractors now collecting data
On fiber that's been installed, but at first they didn't have, they didn't have a consistent standard to use across their platforms. We used the DPC to actually build that out for them. And so now we've got a GIS, a field collection schema, and SML3D GIS schema
that anybody can now use. All the contractors, right? And so once we build it, we share it, so then that way it cleans up a lot of the data before it gets to us.
It can be leveraging FME, the ETL workflows, connected databases. I didn't even get into that. We've got a myriad of different databases that all funnel into the DPC. We have an ACPI for the building smart data dictionary, so we can actually publish out to the BSDD if we want to, or we can import back in from the BSDD.
The next big thing for us is really building out enough of the database to
document all of the relationships, not just the attributes or the feature code library, or feature code name, but all the attributes, including what's driving those assets at that particular state of its lifecycle
And then, yep, and then now we're trying to figure out as a department, you know, get at this point on Devin's jobs. How do we now build a governance team
That actually meets the needs. And one of the things we've been saying for a long time that we learned quite some time ago is that if we want to do new things, we need new ways
And that's all we got. Devin, you want to add anything else?
Yeah, I'll just add, you know, some of the comments that came up during when Jag was presenting before us to, you know, we are looking at ways we can incorporate national standards, open standards. We have a lot of national standards that are already being used
But any of the DOT partners that are here will always tell you that
you know
Going from Europe to the US, there are those differences of many of us states still have very different requirements. So how do we find a middle ground? You know, how do we find a way to connect databases that are in place and help digitize the standards that aren't
Without causing too much strife, you know, anguish of, you know, being able to connect that. Everybody's got an ownership of some part of, you know, their piece of the pie, and, you know, the ultimate vision at the beginning, trying to maybe just simplify it as much as possible is the DPC can help to be that
Rosetta Stone of sorts to help connect all these people, you know, via standards. And, you know, we're happy to share this more with others. We've been talking about this at the ADCMS peer exchanges and other
EDC events for quite some time, but I think Mark really hit it, and, you know, selling it as our big vision is, you know we're not while we are moving forward with, you know the digital delivery and the virtual design and construction aspect and pushing where we can there, all of this needs to come together
in some bigger connection at the end, and this was something we identified early on as maybe a piece that was missing, and as we can see, you know, it's getting adopted elsewhere, you know.
the FHWA has been very keyed in with what we're doing here, and, you know, the NIBS group, it's, you know, leading into where the grant initially started. We could be kind of a testing ground, a proof of concept, if you would
to help see where this could go nationally. So very happy to be able to share this today. And Roger, Matt, I'll turn it back to you for if we've got questions and that
Yeah, thanks. Thanks, Devin. Thanks, Mark. This is great and it really did build on and complement the CBTL
Which still more theoretical at this point, but nice to see that something practical is being done, and you guys are putting rubber to the road, so I think that's really cool
And, I hope we can keep that going, the dialogue, because like you said, Devin, you guys can build something, but I think you're working to
take that content and put it into applications that every DOT is using, or every consultant out there is using. So, you know, we don't… we want to try and leverage. That's a lot of what the pooled funds are trying to do, a lot of what
The DDSG is trying to help
foment is this idea of
bring this powerful community together and leverage things to everyone's benefit. So
It's nice to see how far you've gotten. And I think you can see the parallels in what you're doing and what we talked about in the report we've been working on for Federal Highway about a CBTL and in
The proof of concept that Jag shared with us. I think we got to make sure we kind of
keep pulling together now that we're all out in public on this
So I will go on record and say, too, that when we started this whole effort, it was
self-serving, let's put it that way, you know, we recognize that we had a task we needed to have, so we're just excited to see that it's also getting legs and others are seeing where, you know, similar type of a function, or it can be expanded and help
you know, help grow it. I do see a question from Ashlynn in the chat, the status of or how long is it anticipated to get all the standard plans and 3D features. So
Mark, maybe you could help right here, like, where does the digital products catalog actually handle, physical, like, digital information at this point? But before you do that, Ashlyn, I'll say that's also where we've identified the need for having this
Information framework team, both as a governance and a work group, and those individuals were kind of prioritizing asset information and then working through that. So we're a big organization. What we in project delivery think is important may not be what our performance managers think is important. So
How do we help make sure we're connecting this information and doing it in a way that is going to build? So I can't answer. I can't give you an answer on what our anticipated schedule is right now. We are kind of developing that. But, Mark, maybe you could enlighten what part we have actually accomplished with the initial developments
Sure. Yeah, so we're in the process. We've actually about a year and a half
We've been trying to find consultants. So this is like part of sift. I'm going to drop back a little bit. The Caltrans information framework team. The other reason why it's going to be really important, if you're a DOT, the other reason why it's going to be really important that you start to consider developing a deep bench
of information framework professionals within your organization is because yours we've realized there's no way we're chopping all this wood. It's just not happening. There's no way, right? So to have all of our standard plans into 3D features that would take quite a bit of wood chopping, right? And so where we're at in the process
is where the other function of SIFT is they'll also be the ones that develop the scope of works
and they're the ones that oversee the quality of the product right? And the process between us and our consultants. We just were wrapping up a contract with one of our consultants right now, and a lot of this has come out of that that process, right? Because as they came on board to help us with
creating some of these things, it really blew up a lot of our blind spots. And, and so that's, again, back to this concept of, you know, one thing's having a digital repository, but another thing's having the right type of governance team that can create scopes of work and oversee the work being done.
And then you're going to need some sort of partnership to come in and start to actually produce those features. So to answer your question, how much money do we have, Devin? That's if I want to do the calculations, it's a function of resources and talent
But this is going to be an ongoing process. I think the bulk, I would say the bulk of what you'll see with 3D features could be somewhere in the ballpark of 3 to 5 years. That's that's a that's a fairly aggressive sort of approach. But we've also had poor luck. The last
We try to go out to contract to develop the 3D feature code library for just our drainage.
And we… nobody bid on it.
We didn't get a single bid on that. And so, yeah, so, you know, it's trying to find the talented, the talented consultants that can help you do some of the woodchopping
Yeah.
It would
I do want one more thing real quick before I go, and then we'll then I'll hand it back to you, Roger
I saw Gary Holman on the call. I don't know if Jim is on the call, but the second ADC mess Grant is a joint grant between Caltrans, Oregon, and Washington
And the goal is to basically build out about 15 assets together, and all of those assets will be housed in our DPC.
And the reason being is this is a prototype for a national DPC
Because just imagine, you know, everyone wants a national standard, right? But how do you get a national standard if you can't properly and accurately identify the overlaps and gaps between all the different departments? So I just wanted to say, stay tuned on that one
We just got the funding released, so now we're going through all the interstate agreement stuff. But hopefully this time next year, Oregon, Washington, and Caltrans will have quite a bit of experience to share with this group about what it looks like to take a DPC and open it up to three different DOTs
And then use that for analytics
Jim is here. Rockley, can you find Jim Mayhew? Jim, do you want to say anything about
about this, because you did do a nice presentation for us back in January. I think this ties into the signage effort. Those are assets that you might be working with, right, Mark?
Yep. Yeah, and Gary has said a chat too. He said almost there.
Gotcha.
Oh yeah.
And then
Let's see if we can
Devin and Mark, I'm gonna take co-chair prerogative and jump in before Jim adds, but
I'll just say I'm always excited to hear from you all and what you're all doing. I mean, you're all
I think thinking outside the box and, you know, amazingly generating resources for you to advance these initiatives, and it's all, you know, helping to contribute to the dialogue
nationally. And additionally, I don't know why, Mark, but your delivery, I don't know, is just so calming and soothing to me for some reason.
Like, I need to learn how to deliver like you do.
There are a few questions in the chat that I think we'll get to, but the one thing I wanted to ask just
And probably at a high level, but I'm kind of focusing in somewhat on some of my past experience as a project engineer
Like, where does the construction inspector fit into this, or how are they using and leveraging
what you're doing here for, you know, for their job, or to make their job easier.
Sure, you teed it up. So, Devin, do you mind if I take this one?
Okay, so
Because we have another phrase when we build stuff, we want it to feel like home. We're big on the home concept. So what we've done, you know, with ASHTO, where pre-construction with the bid items, you know there's over like what, 40,000 different items, right?
And what we've done is we've actually connected the DPC to gosh, what's the database called Devin that spits out all those assets per project?
It's been a while
I don't remember now. Yeah. Anyway, the yeah
So, yeah, so we have, I think it's called CAS, I can't remember, but we've got another. Yeah, CAS
Oh yeah, gas. Yeah, yeah, yeah. Our payments, our payment system, yes, yes, yes.
So we have… we basically, per project, what we do is, you know, but our bid items start at, I think, 001 or 0, and then they're just, you know, they just then go chronologically. So, like, one is the… could be a different item on each project
But what we've done is to help the field inspection process feel more like home is in the Dpc. When you put in the say like that contract number, it'll pull the assets from that particular project
And then what it does is it creates a custom feature code library for the inspector in the field, so that it looks just like they're used to, 0 to N, right? But then what we've done is we've baked what's called the feature code
into an attribute, so then that way, when we want to process it all on the back end, we can sort of reverse that. And what that… so it keeps it feeling like home for them. It reduces the noise, so instead of having to go through a catalog of 40,000 items
To try to find that bid item in the data collector. Now, they only have the 20 to 30 to 100 items that are on that project. And so it's a customized per-project feature code library, so it's a customized schema for the inspector to use
that actually reads just like they're used to at reading. And it doesn't read like a survey experience. It reads like an inspector experience. So that's how we've done that
And maybe to add to what Mark is saying, to answer that one question or give an example to the one question of like, why would you have your own state specific?
For Caltrans, how we've, you know, we've got 50, 75, 100 years of bid item information, our bid items, there's bid item codes, and then there's bid item number. Each specific bid item has a very specific, unique identifier code, which that number means something as far as finding information in our specifications.
But on a project, you might only have 100 bid items, and they're sequential. But we've got 40,000. So to Mark's point is this is
applying the Caltrans standards of how you find information about specific materials or bid items within all of our other standards documentation, the linking it with historical information that we have for decades
And making it feel like home for that inspector, doing it in a digital way, and enabling that easier linking of digital information in the field to whatever the digital products that they're using might be.
All said.
And does that… does that get to, like.
A very deep level of a material
Being their, like, constituent properties as well. Like these are, you know the aggregate properties in the pavement
For that particular pavement type
You know, does it have rheological properties of the liquid binder that they can, you know, compare against specification requirements, things at that level
Again, that would be a, you know, per item based on how that information needs to be broken down. Some of our item types are specific. It's class two aggregate base. You know exactly what it is. You go to the standard specs. Then you've got other things where it's continuously reinforced concrete pavement and you could have
You know, sub-items that are part of it. So that's, you know, kind of getting to the detail of what, you know, the devil in the details. What level of attribution needs to be there based on what that might be, and how does every owner in the asset throughout the life cycle of your infrastructure, not just your project, your infrastructure
going to be touching that. So you know of the main point of what we've actually developed in the Dpc. So far is helping with that handover from design to construction. But we have the long vision of like trying to connect all this other these other items that
How does that then lead into our performance managers, which are separate from our asset managers, which is separate from ops? And, you know, what is the, you know, the information they need to get out of it, and how do we
Continue building that Rosetta Stone so people can get the information when they need it, how they need it, the way they need it, and what they want it to look like. So
And hopefully, as you guys are building that, you're using the standards that you can find that are out there, like
Objects are identified in IFC, so if that's a starting point for an object, it has some properties already attached to it. Surely you have different ones, but some of them are similar, and it's a mapping exercise, so that's a great leg up on
Everyone else connecting with this by using that as a sort of foundational approach.
Hey, Roger, we'll take it a step further too. So
We could probably share this once we're done with it. We'll be wrapping this up at the end of the year. So what we've done is we're creating kind of like an ATM experience, right, with
spreadsheet templates, and in our spreadsheet templates, that's what our consultants are using right now. So we'll have drainage, safety devices, and I can't remember the other one, drainage… there's another category. But we'll have these done by the end of the year
And the idea is, so you can take this template and it tracks all of that, Roger. So to Trisha's credit, we've got quite a bit of MnDOT stuff sort of baked into some of these things and different pool fund studies, and we track all of the different components
Hmm.
to the source of the creator, right? And then that way, as it's in there, we can we can kind of slice through it, we can query through it if we want to as well. But that's all in this spreadsheet template that we've been developing over the last 6 months. So then that way, it's
Yeah.
Because not everyone's going to necessarily want to use the DPC. Some people, some folks just like to excel. They just love it, Roger. It's like their love language. That's how they see the world, right? And so we're trying to kind of be as much as
what the different people need us to be so that they can just be who they are and sort of do the work. So maybe we can come back, you know beginning of 2027, too, and we can showcase some of that process. We've actually hired a consultant from Europe to help our consultants, so we're really trying to take the Big 10 approach
Where, you know, we're all growing together, even our consultants. So to be a DOT and to expect anyone to have like a full monopoly on how all this works is unrealistic. And so I think one of the best things we can do is to try to try to create more collaborative experiences
And we'll get better results. At least that's what we're seeing now.
Devin, is that is that how you're seeing it?
Yep.
Yeah.
Yeah, that's great, Mark. That would be great. One of our main purposes here is to get information out about who's doing what so people know what you guys are up to and don't go off and reinvent the wheel somewhere else, but reach out. So the more we can keep this kind of discussion
Okay
collaboration going, the better. And I have to point out, in the chat, there's a question about Toby versus IFC. So, the spreadsheet approach is definitely popular and good. There's a lot you can do with a worksheet.
Well, I'll go ahead and say like the use of IFC versus native file types, that's a question that depending on what the user needs, how they're going to use it. I don't think
Many folks in our BIM program don't see IFC as a smoking gun that's going to solve all of this. It's going to be, what's the right fit for the right purpose. So, you know, we're not getting tied… we're not tying ourselves to IFC only
It's more, from our perspective, again, is like, how does somebody need it? In what format, in what way? And, you know, we're more of
Not trying to break everything just to fit into one mold of a file type, but what is the right way to share the information?
Right.
Well, either or also because objects are objects and it's nice if you can align with ISC, that helps down the road and then you can use it in your native file format too. So
You know.
Your DSD helps with that.
Ultimately, one thing that we always talk about is no matter what we do, no matter how fancy or advanced we make our digital products.
Ultimately, we're we're maintaining and building infrastructure. If the people that actually build it for us can't build it, it's not beneficial. So you know there's going to be plenty of times where as much as we digitize this information, you're still going to have somebody that wants to have
You know, a carpenter is still going to want to have a 2D set of plans to know how to build a head wall and take measurements off of it. So how do we enable, you know, our contractors and our building industry to be able to meet the goals that we're putting before them
So, to your point, Roger, it's, you know, if you can digitize this, you can connect it, and you can deliver it in different formats, but ultimately, it's like, what's the end product that you're really trying to deliver? Who… who is it that you need to actually
Yeah.
You know, make it come to life otherwise you're modeling for nothing. It's not going to be beneficial. And maybe that kind of goes a little bit into the last question I saw here from Sahab
You know, how the BIM data's gonna fit into the different, you know, pavement systems and that. That's part of our information framework team. You know, we… I'll use one example, culverts. We have our maintenance program has a very sound
Covert database
But in order to get information into the culvert database, we have designers who design it. We have construction staff who go and inspect it and document it and as built it, and then we have maintenance guys who go back out and locate it and identify it and inspect it.
There's a… there's a break in the system there of how do we just enable a way of a digital transformation where they don't have to go locate it, they just show up 10 years later and start their inspection. They're not spending duplicate time there. But each system, some are GIS systems, some are, you know, tabular
Part of our efforts are, you know, how do we
How do we connect with the appropriate systems as necessary? Do we break a system? Do we work with them to say there's a better way to do this? And are they, you know, is the change management there for it? To Mark's point, you know, in his last slide, you know, sometimes you got to do new things, new ways
And does that mean you completely replace an old system or we find better ways to connect to it and eliminate eliminate redundant processes and extra work
Yeah, and this is why we like to reference this paradigm shift as our digital cathedral, right? It's Devin and I, this is like an infinite game we're playing now, right? This isn't a baseball game. You talked a lot about building the stadium, but
This is that infinite game theory that I'm sure you've all seen the Simon stuff.
And so we've got to be looking at 5, 10, 15, 20 years. And so part of the process of developing the digital systems is making sure we're developing the analog systems. So I can't stress this enough, probably what we've kind of realized is one of the most critical, if not the most critical
that sort of path item for us right now is to develop our people to become more informational minded. Well, I'm not going to air our dirty laundry on a call like this, but let's just say like, and I don't like calling it change management. This is so much bigger than change management. This is going like
Like, from drafting board to CAD, it's that, I think, but on a more exponential curve going from CAD into an information framework mindset. And so what you're going to see us do over the next 24 months is you're going to see a lot of resources and support
Port into people. Again, not change management. This is like real sort of paradigm shifting like people development. And so you don't want to wait till it's all your digital stuff's built like the people part
And we're happy to share what we're doing with everybody because we're kind of feeling our way across the river. So if anyone else is doing something similar to us, we'd love to sort of
you know, trade pain points and lessons learned. But you're gonna see a lot of investment into our people over the next two years.
Jim's been very patient before I jumped the line, so let's, let's let Jim come in.
Thanks for that.
Oh, I didn't want to steal any thunder. These guys are doing great.
So Washington State is doing a lot of work on traffic signs specifically associated with data dictionary. And we are working in partnership with California and Oregon to try to bring that into effectively
tri-state experience. So I haven't actually reminded me, Mark, I still haven't gotten access to look at your DPC. But I sent an email off to the guy just while you were talking to kind of get that because I think you were on vacation, but
Our intent, like this really honestly takes us into more of a cross-state national view to kind of be able to share things. I think that's really if you saw
If you listened to what was happening in these conversations over the last few days, you know, national standards and working together so that we don't have to reinvent the wheel when a new state comes online or a state tries to apply these things is kind of really important to all of us
In Washington State's right there with that in this effort with Caltrans and ODOT
Be happy to talk with anybody and share information. Just to reach out to me.
Great. Thank you, Jim. Yeah, we still remember what you shared with us about the signage work that was exciting. So yeah, maybe we can get an update from you sometime in the future on that effort and how this all fits together with what Caltrans is doing. That would
Pretty interesting.
I think in about a year, I can also come back if we're still doing this then, and talk a lot to what Matthew was asking about, about how construction does things, and because we're trying to build a construction application right now.
Interesting.
Great.
There was one early question. I think we might well I don't know if we hit it or not, but I'm going to ask it again just in case we didn't put
It was about the DWG to DGN conversion, and what platforms are you using
Yeah, for that one, we're using FME. I think they call it FME flow. I think they rebranded that, so
We're just using the FME flow
Gotcha. And then, Amy, if you'd like to get together, we can get you… we can sync up and show you how we're doing it.
Yeah, so we have a phrase, I don't want this phrase to get misappropriated, but we like to say we're trying to empower people to vote with their clicks.
Right? And so what that means is if we can digitize and centralize our standards, we can do a lot of the back-end work that'll allow things to feel like home, or an experience of a single source of truth, even though we're sort of tying things together for them on the back end
And so, yeah, so I just want to like voting with your clicks, right? I'm not interested in a microstation civil 3D fight. I don't care. I've used them all. They all suck. They're all great. They're all everything, right? They've got pros and cons. That's my point. So like
Like, like, if there's an Autodesk or a Bentley person here, I mean that in jest. I love you both. But what we're interested in is meeting people where they're at, and that's what the DPC represents. We're trying to take the, like, a larger like a lion's share of the work onto ourselves at headquarters
in Caltrans. So then the the actual users in the field
They experience the most minimal amount of change, right? And so for our inspectors, we've created an experience that feels like home for them.
in the new system. So when they jump onto it, it's it's just a better way of doing business, but it's still looks the way they're used to it looking right? So that's that's another big advantage of having a digital products catalog, and then starting to leverage things like FME or other tools
Right.
Yeah, that's great. Well, maybe we'll wrap up this piece there and save a little time to do our last polling, Matt, and wrap things up. I think this has been really interesting. Devin and Mark, there's good to get the word out. There's a lot going on out there
Aaron Constance here, who presented earlier. He's chair of NIB's Digital Technology Council's Digital Delivery Committee. They're working on a lot of these things. We had a
product data group going, trying to bring building product data into a structure that could be shared in a product catalog. So, you know, the approaches are all the same, and this all helps us get there, I think, by sharing this way, and Aaron, I think you got some stuff to follow up on
Yeah.
with these guys. So you can do that after the fact. I'm sure you know how to reach them. We've got a couple of… oh, did you want to say something quick, Aaron? Because we want to
Yeah, since you mentioned it, great presentation, right? This is exactly what we're working on at the NIBS Digital Technology Council just was reformatted. Not sure if you're familiar, but there are three main committees, Digital Twin, field technologies, and I'm the chair of digital delivery
And so this is exactly what we're looking into, and you hit the point, right? There's so many standards. How do you choose one? And, you know, from the national BIM standard that we had this discussions, and Roger's been
A part of this work is we're kind of looking towards going away from standardizations versus frameworks of adoption of standards and mitigations
So
That's it
All right, Aaron, I got to cut you off because we got things we want to
Well said.
Yep. So please, yeah, please reach out and let's get with that.
So you can follow up with these guys and make the connection. So yeah, Mona put a link in the chat. There's also a
QR code. If I can share, I'll put that up
Yeah, I think Mona might have to send the link. I didn't get it either. It says full message cannot be displayed
Oh, there it is
So the link is inside the chat here. You guys can click on the most recent link that was just dropped in.
Thank you.
Yeah.
And there's the QR code should be on the screen now.
So we've got two CBTL courses
Is it, Mona? Is the QR code
It is, yeah, so the two QR codes and the link are in there. So
We just have a short minute here because we're almost out of time, but yeah
Yeah, no worries. So I think most of you have really come in already and answered the first question, and I'm glad that we put that question up early because you guys were dropping in really good feedback for us while we were presenting earlier and when Jag was presenting and now with Caltrans. So I'll move on to the second question here
What would you like to explore further during the September CBTL workshop? So this is pretty broad, but if after hearing from everybody speak today, you have a focus in mind or things that you really would love for us to focus on in September related to the CBTL, please let us know. We want to welcome everybody's feedback here
I thought I had that open.
And what I'll… I can share my screen, Roger. Let me share.
Please do, because the code's not working.
For me. Okay.
There you are. So we're seeing information come through data integration and showing how the model connects, use cases from the everyday end user perspective. I love that connections between divisions from design to construction.
And we had really great comments and feedback in the last question that we just asked, so we'll make sure to combine both of those items. There were some questions requiring and requesting more clarity. There was one comment in there that was concerned about, you know, building it is one thing, but then maintaining it is a whole nother
challenge on its own. So, you know, sustainability of the CBTL long-term, I think, was one of the several comments that we received in the last question.
How can a federal group take on ownership of a national library and framework that DOTs can't connect with? That's a good one.
That's right.
Yeah, great. Can this stay open? Mona, I know we also have our closing poll or one will conflict with the other, I guess.
Yeah, we could take one more, maybe 30 more seconds for anybody that wants to add any questions, and then what we'll do is I'll stop sharing this and then if someone from the NIBS admin team can drop the closing questions link one more time for everybody, we'll switch over to a second survey
And it'll be the last questions that we ask. It's the same if you've attended the last two days. We really want to understand if you found today's session valuable, and if you have any comments related to today's content and sessions overall.
You know, this one here is particularly relevant to get feedback in, so we'll try and leave that open as long as we can.
Here, while we have everybody's attention
And the other survey, the second link, the one that ends with XD3, that is to the closing questions, and that is an on-demand survey. So you can click that link and take that survey even after we drop off of the call. If you think of anything
knew that you'd like to share. There is an open field that can relate to the CBTL or can relate to really anything that you'd like to see as an outcome of today or just the last three days. So we'll keep that survey open for a couple days, and you can jump back in and add more feedback later as well.
Thanks so much, Mona. I'll remind everybody, too, that the mural board will also remain open
So if you have any thoughts that pop into your mind afterwards or tomorrow, or next week, you can always
Go back in to the mural and, you know, add your question or sticky note, etc. Those will be a resource that we maintain, so you can even go back to reference them later on
We will be posting the recordings for the meetings at the DDSG Hub as soon as we get everything processed
Through the platform, and we'll get those up another reminder is that our next scheduled meeting, which will be
The in-person meeting, which also will have a virtual component, but we will be meeting the last two full days in September
Here in Northern Virginia, International Highway Institute
Office location, which is in the larger Washington, DC metropolitan area. But just here across the river in in Northern Virginia.
Those two full days, the last two days in September, you'll see more information
Regarding that meeting at the Ddsg Hub as well. And we'll be posting
The registration links and things, etc. here shortly as we get a few things finalized and wrapped up there
And
Matt, one final note about the September meeting that's going to happen on the 29th and 30th. We are actively, we're switching which organization we do our in-person registrations with. So when that is finished, we will be sending out an email blast to everybody.
They can go ahead and get registered. Same thing, the virtual portion, because this will be a hybrid meeting, meaning you can also attend virtually as well
We will be working through that, and then that will also be in that email, so for both different registrations, whether you're in person or virtual, do look out for an email from us.
Thanks, Raklee.
And to wrap things up, I will first express my sincere appreciation to the speakers and the presenters and engaging the group
And more importantly
To you, the participants here that have taken the time out of your very busy days and schedules
And remain engaged in the conversation and with us. Much appreciated. I feel blessed to be involved with this group in this effort and continue this communications
and we will see you in September. Thanks a lot, everybody.
Have a great day.
Yeah, thanks. Thanks, Matt. Thanks, everyone. Good to see you all.
Alrighty, I'm going to close out the webinar. Thank you, everyone.