October 2026 Digital Delivery Newsletter

Hello TxDOT staff and partners,

It’s Halloween time in Texas, but we want to remind you that there is nothing spooky about digital delivery. The October 2026 edition of the TxDOT Digital Delivery Newsletter highlights continued advancement with updates focused on people, projects, processes, and training. This issue shares an important milestone update for the Paris District’s FM 44 pilot project as it moves from design and letting toward construction.

The newsletter also explores major improvements to the Right of Way Utility & Leasing Information System (RULIS), including integration with existing TxDOT systems, expanded use of GIS-enabled data, and emerging tools for utility identification and conflict management. We dive into how utility conflict management, automated clash detection, and digital agreements will establish more consistent, transparent, and collaborative workflows across utility coordination, design, and project delivery. We also highlight how we are preparing TxDOT staff and industry partners for broader implementation through Contractor Summits, technical digital delivery training sessions at the 2026 TxDOT Short Course, frequently asked questions, and updated training opportunities.

Together, these articles and our ever-expanding resources demonstrate how TxDOT is supporting the transition to more digital and connected model-based workflows, while fostering collaboration and building the knowledge needed to implement digital delivery consistently across the project lifecycle.

Thank you,

Jacob Tambunga, P.E.

Director, Digital Delivery

Project Overview

The Paris District FM 44 pilot project consists of the design, letting, and construction of a bridge replacement on FM 44 over White Oak Creek in Red River County. The project is TxDOT’s second pilot project to let using digital delivery methods and the first to include a bridge. The design was developed in-house by the Paris District and Bridge Division and is now moving into bidding and contractor selection.

What was the most valuable benefit of using Digital Delivery on this project?

Paris District develops PS&E for many bridge replacements each year and this allowed the design team the opportunity to improve and advance our 3D modeling skills and knowledge.

How did the Digital Delivery approach differ from the traditonal project development and letting process?

With our project being an on-system bridge replacement, a lot of the initial approach was the same. We found that there was still the need to produce several of the same plan sheets as a traditional letting to provide consistent record retention across other departments and agencies. A couple of differences would be the model needed to have intelligence added and be more refined than a traditional project. Also, with this being our first digital delivery project, there was more coordination that needed to happen between departments.

What were the most significant challenges or lessons learned during the pilot?

One of the lessons learned for our team would be to understand the Level of Development early on for bid items. Having a clear definition of LOD per bid item and how those items incorporate into the model, will help minimize modeling difficulties in later stages of design. Another lesson learned would be to verify the excavation and embankment quantities that the model report gives. We noticed that the excavation quantities given in the model report had added in some areas that should have been considered subsidiary to another bid item.

The project received seven bids with a low bid of $1,792,908.20—which was approximately 0.5% over the Engineer’s Estimate of $1,783,455.25. What does the successful letting mean for the project team and the Paris District?

Our district does consider this to be a successful letting since it let on time and close to the estimate. Now we will be looking at construction to see if the deliverables we provided were beneficial to the project or if we need to add or change something for next time.

What advice would you offer other districts preparing to deliver their first Digital Delivery pilot project?

One thing we would recommend is to allow enough time for design. With everything still being new and everyone learning new things, there could be situations come up that may take time to figure out. Depending on what changes need to be made, it could take longer than a traditional bridge replacement project.

The Right of Way Utility & Leasing Information System (RULIS) program is beginning to go through some updates. The program overall continues to manage TxDOT's utility and real estate business processes through program management, but with updates to digital delivery, RULIS will begin to go through some process optimization to better integrate and coordinate with updated digital delivery processes.

RULIS mainly is used by two different TxDOT sections:

• Utility Portfolio Section: Oversees the TxDOT Utility Coordination and Accommodation program. Includes utility permits and utility agreements in support of transportation projects.
• Real Estate Services: Oversees the sale, transfer, exchange, and leasing of department owned real property. Includes management of saltwater pipeline and real property leases.

Overall, RULIS serves as a centralized platform supporting utility coordination, permitting, agreements, leasing, and real estate transactions across all TxDOT Districts and projects.

Updates to RULIS will allow for more integration in GIS mapping, data collection, and TxDOT systems such as TxDOTCONNECT, OnBase, ProjectWise, and EDP Snowflake. The system's single-account mode allows for quick access to online lease payments, mobile inspection requests, and has multi-browser accessibility. This promotes transparency and consistency for users statewide.

Looking ahead, RULIS continues to expand its capabilities with future enhancements focused on utility conflict management, standardized utility agreements, and reimbursement processes. Additionally, the Right of Way Division is leveraging 4Map (4M), an artificial intelligence tool, to increase efficiency in identifying utilities within transportation projects which helps with better project delivery.

These updates will provide staff with a comprehensive, data-driven solution for managing right of way, utility, and leasing activities. Check out the article below for more information pertinent to utility conflict management and right of way applications.

RULIS Resources

If you have any questions on RULIS and what this means to you, don’t hesitate to contact the following emails:

• Utility requests: ROW_UtilityRequests@txdot.gov
• RULIS access and applications: ROW_Applications_Helpdesk@txdot.gov

Additional links to trainings and resources are included below:

• RULIS training for external partners
• Crossroads
• Utility Accommodations Toolkit

Over the years, the evolution of TxDOT’s utility management technology has seen operational improvements in efficiency, transparency, and collaboration across the state. The legacy Utility Installation Review (UIR) system had become outdated and was limited to Internet Explorer, creating operational challenges for users. The introduction of TxDOTCONNECT (TxC) has modernized project coordination by consolidating project information into a single platform, allowing users to access construction and project data without navigating multiple systems. TxC also streamlined utility processes by enabling the creation of utility identification numbers (U-numbers) directly within the system, eliminating the need for separate requests and reducing staff effort.

RULIS Utility Permitting has now replaced UIR with a more modern and integrated platform that provides single sign-on access for both internal and external users, eliminating the need for separate logins across districts and devices. RULIS also incorporates GIS-enabled capabilities, automated business rules, enhanced reporting, and improved visibility into permit approval timelines, resulting in more consistent and transparent utility permitting processes. The system also functions as a repository for utility as-built records and subsurface utility engineering deliverables, transmitting finalized records directly to ProjectWise and eliminating redundant uploads.

Workflow

The updated Utility Conflict Management (UCM) process is designed to standardize utility conflict management statewide, create a single source for utility coordination activities, improve communication and collaboration among stakeholders, and strengthen the connection between utility coordination, design, and project delivery. The workflow below eliminates inefficiencies by providing a centralized platform where districts, ROW Division, designers, utility owners, and consultants work from the same conflict record throughout the project lifecycle.

Step 1: Project Initiation

The workflow begins in TxDOTCONNECT, where a project is created and utility resources are approved. Once established, project information automatically flows into RULIS UCM, providing the foundation for utility conflict management activities.

Step 2: Utility Organization Mapping

Utility companies are mapped to a corresponding RULIS organizational unit. This mapping controls system permissions, access to conflicts, utility-specific project nodes, comments, communications, and document management, ensuring that stakeholders only access information relevant to their organization.

Step 3: Design File Integration

ProjectWise remains the official system of record for design files. To begin integration, the project designer enters the ProjectWise URL into UCM, initiating synchronization through Bentley iTwin technology.

Step 4: Conflict Identification and Visualization

Clash detection results generated in Bentley OpenRoads Designer (ORD) are converted into three-dimensional conflict geometry and synchronized through iTwin. These conflicts become visible within UCM's 3D environment, while key conflict attributes populate the UCM conflict table for tracking and management.

Step 5: Manual Conflict Creation

Not all conflicts originate from design software. During utility coordination meetings, users can manually create conflicts in UCM. After review and approval, these conflicts are exported back to ORD, ensuring consistency between design and coordination activities.

Step 6: Conflict Management and Communication

The conflict matrix serves as the primary working tool for project teams. Users can apply filters, freeze columns, view active conflicts, and track conflict-specific comments. Collaboration is streamlined through comment tagging, which automatically generates email notifications whenever a stakeholder's response or action is required.

Step 7: Centralized Coordination

UCM brings all coordination activities into a single platform, including:

• SUE and as-built utility data
• Project comments and communication logs
• Document uploads and management
• Utility coordination records
• Project resources
• Meeting scheduling and coordination activities

Step 8: Reporting and Data Sharing

Data maintained within UCM, including comments, communications, and conflict history, can be exported for reporting and analysis. Information supports project huddles, executive reporting, Operational Performance Centers (OPC), Tableau dashboards, and other business intelligence needs.

The Future of Coordination: Utility Conflict Management

The future of utility coordination at TxDOT is centered on Utility Conflict Management (UCM), a comprehensive solution designed to connect utility coordination, design, and project delivery within a single collaborative environment. By leveraging project information directly from TxDOTCONNECT, utility coordinators no longer need to re-enter project data, reducing administrative effort and improving data accuracy. SUE and as-built data are readily available at the project level, providing designers and coordinators with immediate access to critical information. Utility companies are mapped to RULIS organizational units, enabling a consistent framework for permissions, conflict access, communications, document management, and utility-specific project activities. At the core of the system is the conflict matrix, which combines design files, alignment data, and utility conflicts within a geographic environment and provides advanced tools such as filtering, frozen columns, and active-conflict views. Conflict-level comments and user tagging ensure all discussions remain tied to the conflict record while automatically generating notifications when action is required. The platform further consolidates coordination activities by integrating project resources, communication logs, document uploads, and meeting scheduling into a single workspace. Conflicts can be generated through automated clash detection or manually during utility coordination meetings, with standardized templates ensuring consistency across projects. All conflict data, comments, and communication history are exportable for reporting, OPC and Tableau dashboards, and project huddles. With work packages one through three complete and configuration, development, and system integrations currently underway, the program is advancing toward user acceptance testing, training, and change management activities, with statewide deployment targeted for September 2027.

The Future of Coordination: Utility Conflict Clash Detection

Utility Conflict Clash Detection represents a major advancement in how TxDOT identifies and manages utility conflicts throughout project development. Today, districts often rely on static documents, Bentley ORD files, and manually maintained spreadsheets to track conflicts. The future workflow automates this process by leveraging clash detection technology integrated directly with ProjectWise, which remains the system of record for design files. Designers simply enter the ProjectWise URL into Utility Conflict Management (UCM) to initiate synchronization through Bentley iTwin, eliminating the need for separate file uploads. Clash detection results from ORD are transformed into visual 3D conflict geometry and displayed within UCM, allowing users to view conflicts in a geographic environment alongside design and alignment data. The current proof of concept displays conflicts as disks, with future enhancements moving to spheres to improve visibility within the 3D model. Selected conflict information flows automatically into the UCM conflict matrix, eliminating manual data entry and creating a seamless connection between design and utility coordination. The process works in both directions, allowing conflicts identified during utility coordination meetings to be created in UCM and, once approved, exported back into ORD for incorporation into the design workflow. Behind the scenes, TxDOT is partnering with the Design Division to expand the utility cell library so that BIM and ORD models more accurately represent real-world utility infrastructure, including telecommunications, duct banks, water, wastewater, gas, and electric facilities. This capability supports TxDOT’s requirement for GIS-based 3D conflict visualization while maintaining compatibility with both ORD and BIM environments. By identifying conflicts during 30%, 60%, and 90% design reviews, long-lead utility issues can be addressed earlier, reducing redesigns, claims, schedule impacts, and project delays. Ultimately, clash detection becomes the engine that feeds the UCM conflict matrix, allowing design teams and utility coordinators to collaborate using a single, shared conflict record throughout the project lifecycle.

The Future of Coordination: Agreements and Reimbursements

The future Agreements and Reimbursements workflow will eliminate paper-based forms and PDF packages by creating a fully digital process with a single source of communication for utility owners, consultants, districts, divisions, and leadership. Through integrations with DocuSign, OnBase, and TxDOTCONNECT, stakeholders will be able to collaborate, review, approve, and track agreements and reimbursements within a streamlined workflow that supports transparent, efficient, and centralized communication from initiation through final approval.

The digital delivery program was featured in two dedicated technical sessions at the 2026 TxDOT Short Course, held on Tuesday, October 13. The two sessions, titled Digital Delivery A and Digital Delivery B, provided attendees with a comprehensive look at how digital delivery is being implemented and advancing across planning, design, construction, inspection, asset management, and maintenance, for all projects across TxDOT. Attendees were given insight into the current progress, lessons learned, and the long-term vision for delivering, managing, and maintaining TxDOT projects and infrastructure through connected digital workflows.

“Digital Delivery A” focused on program-wide progress, data governance, and lessons learned to date. Presentations covered TxDOT's Digital Delivery implementation efforts, the importance of data governance in supporting reliable and reusable project information, and real-world experiences from districts participating in the Digital Delivery pilots.

“Digital Delivery B” was primarily focused on multidisciplinary collaboration, construction implementation, and lifecycle data use. Topics included how to integrate digital delivery across utilities, environmental, geotechnical, and hydraulic disciplines; supporting inspection and construction management through model-based workflows; and exploring how project data can ultimately support asset management and long-term maintenance planning.

The combined sessions highlight that digital delivery is more than just a technology initiative. It is an over-arching programmatic transformation that connects people, processes, and data across the entire project lifecycle.

Here are a few of the questions we received from the districts this last quarter:

• I hear Bentley Infrastructure Cloud (BIC) and iTwin used interchangeable. What is the difference between the two names?

Bentley Infrastructure Cloud (BIC) is Bentley’s current name for the online platform used to access and manage iTwin models. The platform was previously referred to as iTwin, and some users may continue to use that terminology. While the terminology has evolved over time, some users may still refer to the platform as iTwin. In this context, both terms refer to the same platform.

• What if the district absolutely needs PDFs to submit to other agencies or leadership?

In accordance with the Digital Delivery Initiative, only a limited reduced plan set will be approved. The reduced plan set will typically consist of a cover page, file index, quantities, TCP Narrative, Special Provision 000, and all applicable standards. Any additional PDF deliverables outside of the approved reduced plan set must be reviewed and approved by Jacob Tambunga prior to their creation.

• When syncing a file in Bentley Infrastructure Cloud, I cannot see the status progress bar while it’s syncing or the errors, issues, warnings the model has when syncing.

Access to this information is determined by the user roles established during the initial project setup. Currently, project progress is visible to the Model Manager and Project Manager based on their assigned management roles. We recognize the value of providing greater visibility and are evaluating options to make this information available to all project users.

• In ProjectWise, my consultant working on my pilot project can only see the roadway folder. How can they make container files for iTwin when they can’t reference all the files?

ProjectWise access is determined by the roles assigned to each user. Consultants are assigned zy_EDC-Design rights, which provide them with the same capabilities as TxDOT employees within the Roadway folder, and within the Bridge folder when designated as bridge personnel, except for the ability to delete files. File deletion permissions are limited to the district’s Design and Bridge teams. We recognize the benefit of providing consultants with view-only access to other project folders and are currently exploring access modification to accommodate this need.

• In Bentley Infrastructure Cloud (BIC), I cannot see the weather status or the cover photo at the top of my landing page which displays the weather where my project is located.

Photos can be added at any time; however, the weather widget is dependent on the geographic coordinates of the project location, which are provided to ITD when the project is initially created. Moving forward, we will make every effort to include these coordinates when creating new projects. For existing projects that do not currently have the weather widget, please contact your designated Design Division representative if you would like to have it added.

• When making comments in the iTwin model during district review, it is an unnecessary use of time to continue to fill out the name and date of the person who created the Comment (Issue) when we need to log into our account to make the comment. Can we update the form to auto populate the name and date of when a form is created so the reviewer can only fill out the discipline and comment?

This is a valid point and an issue we have not encountered during previous pilot projects. Auto-populating the name and date fields would improve the form’s efficiency, and we are currently evaluating this update for the next version.