SMART Infrastructure Act of 2025
- Sponsor
- Sen. Lummis, Cynthia M. [R-WY]
- Committees
- Commerce, Science, and Transportation Committee (primary)
- Last action
- Nov 20, 2025
Bottom line
This bill aims to modernize and accelerate federal permitting for transportation infrastructure projects by leveraging digital twin technology and a centralized e-NEPA portal, with the goal of reducing review timelines and improving transparency.
What it actually does
This bill mandates the Secretary of Transportation to establish guidelines for integrating digital twin technology into the permitting process for covered infrastructure projects and to create a pilot program to test its applications. It also requires the development of a centralized, web-based e-NEPA portal for managing, submitting, and tracking environmental review documents, with mandatory use for federal agencies by 2028. The goal is to reduce NEPA review timelines for eligible projects by at least 25%.
Proponents argue
Proponents argue that the bill will significantly reduce delays in infrastructure project development by improving coordination, communication, and data handling through digital technologies, ultimately supporting economic growth and maintaining environmental protections. They emphasize the benefits of digital twins for accuracy, efficiency, and risk reduction, and the portal for transparency and streamlined reviews.
Opponents contend
Critics might argue that mandating new, complex digital systems could introduce new technical challenges, cybersecurity risks, and significant upfront costs, potentially leading to implementation delays or unforeseen complications rather than acceleration. Concerns could also be raised about the potential for digital models to oversimplify complex environmental impacts or exclude stakeholders less familiar with advanced technologies.
The bill is concise and its core provisions are clearly stated, making it accessible for an informed reader to understand its main objectives and mechanisms within a short timeframe.
Section 4(a)
Digital Twin Technology Guidelines
This provision requires the Secretary of Transportation, in coordination with other federal agencies, to establish guidelines within 18 months for integrating digital twin technology into the permitting process for covered infrastructure projects. These guidelines must include standards for creating and maintaining digital twins, ensuring interoperability with existing federal systems, and protocols for real-time data integration, with a recommendation for open application programming interfaces.
Supporters argue
Supporters argue these guidelines will standardize the use of advanced modeling, leading to more accurate impact assessments, reduced project risk, and faster project delivery by improving communication and data quality.
Critics contend
Critics might express concerns about the cost and technical expertise required for agencies and project developers to adopt these new standards, potentially creating barriers for smaller entities or those with less access to advanced technology.
Tradeoffs
Balances the desire for technological advancement and efficiency with the potential for increased initial compliance costs and the need for robust cybersecurity and data privacy measures.
Section 4(b)
Digital Twin Pilot Program
This section mandates the Secretary to establish a pilot program within 120 days to test digital twin applications on at least 10 diverse covered infrastructure projects. The program will evaluate reductions in permitting timelines, improvements in environmental impact assessments, cost savings, and stakeholder collaboration outcomes, with a report due to Congress within two years.
Section 5(a)
E-NEPA Portal Development
This provision requires the Secretary of Transportation, in coordination with CEQ, EPA, and the Secretary of Commerce, to develop a centralized, web-based e-NEPA portal for covered infrastructure projects within two years. This portal must serve as a platform for submitting, reviewing, and tracking e-NEPA documents, integrate with digital twin models, provide public access to non-sensitive documents and comment periods, and ensure secure data storage.
Section 5(b)
Mandatory E-NEPA Portal Use and Coordination
Starting January 1, 2028, all federal agencies involved in environmental reviews for covered infrastructure projects must use the e-NEPA portal. The Secretary of Transportation will oversee this coordination and ensure compliance with statutory deadlines, and a single environmental document will be used across agencies for each project.
Section 6(a)
Accelerated Review Timelines
The Secretary is directed to use existing authorities to reduce NEPA environmental review timelines for "eligible projects" (those using digital twins and the e-NEPA portal) by at least 25% compared to current averages. Guidance or regulations to implement this must be promulgated within one year.
Section 7
Annual Progress Report
The Secretary is required to submit an annual report to Congress detailing progress on integrating digital twin technology and the e-NEPA portal, reductions in permitting timelines and costs, and environmental, public stakeholder, or community outcomes resulting from their use.
The bill's mandate for accelerated permitting timelines (a 25% reduction) applies only to "eligible projects," which are defined as covered infrastructure projects that utilize both digital twin technology and the e-NEPA portal.
Section 3(4) (Definition of "eligible project") and Section 6(a) (Streamlined Reviews)
Why it matters:This is standard legislative practice to define terms early and then use them consistently. It ensures precision in application rather than being intentionally evasive.
Case for: Proponents would argue that this condition ensures that the benefits of accelerated permitting are directly tied to the adoption of the very technologies designed to enable those efficiencies, preventing projects from claiming accelerated review without fully implementing the new digital processes.
Case against: Critics might argue that this creates a two-tiered system, potentially disadvantaging projects that face barriers to adopting both technologies simultaneously, or that it could be seen as an indirect mandate for technology adoption rather than a flexible incentive.
Estimated impact: This condition significantly narrows the scope of projects that will immediately benefit from the mandated 25% reduction in NEPA review timelines, limiting it to early adopters of both digital twin and e-NEPA portal technologies.
The guidelines for digital twin technology are recommended to include that digital twins be developed with open application programming interfaces (APIs), which are open source, machine-readable specifications facilitating data exchange between different systems and vendors.
Section 4(a)(2)(B)
Why it matters:This is standard legislative practice for technical details within broader mandates. It ensures a specific technical approach without elevating it to a primary, standalone provision.
Case for: Proponents would argue that requiring open APIs is crucial for ensuring interoperability, preventing vendor lock-in, fostering innovation, and allowing for seamless data exchange across diverse engineering software tools, which is essential for the long-term success of digital twin adoption.
Case against: Some might argue that mandating or even recommending specific technical architectures could limit flexibility or innovation, or that proprietary solutions might offer certain advantages in specific contexts. However, "open API" is generally seen as a positive for interoperability.
Estimated impact: This recommendation, if adopted in the guidelines, would significantly influence the technical architecture and ecosystem of digital twin development for federal infrastructure projects, promoting a more open and integrated environment.