Dashboard for MILCON Projects Act
- Sponsor
- Rep. Bacon, Don [R-NE-2]
- Committees
- Armed Services Committee (primary)
- Last action
- Sep 17, 2026
Bottom line
This bill establishes a centralized digital dashboard to enhance transparency and oversight of military construction projects for RDT&E facilities within the Department of Defense.
What it actually does
This bill mandates the Under Secretary of Defense for Research and Engineering to establish a central dashboard within one year to monitor and track military construction projects for Research, Development, Test, and Evaluation (RDT&E) facilities across all military departments. The dashboard must display key data such as facility location, condition, age, and programmed civil engineering projects, as well as track unfunded facility requirements. The authority for the dashboard terminates on December 30, 2030.
Proponents argue
Supporters argue that a centralized dashboard will significantly improve the Department of Defense's ability to manage and oversee critical RDT&E infrastructure, leading to more efficient resource allocation, better project execution, and increased accountability. They contend it will provide a clearer, consolidated picture of facility conditions and unfunded needs, enabling more informed decision-making and preventing costly delays or mismanagement.
Opponents contend
Critics might argue that establishing and maintaining such a dashboard could incur significant administrative costs and divert resources from actual RDT&E projects or other pressing defense priorities. They might also contend that existing financial management tools and reporting mechanisms are sufficient, and adding another layer of bureaucracy might not yield substantial improvements in efficiency or transparency.
The bill is very short and can be read quickly, allowing ample time for detailed consideration of its implications.
Section 2(a)
Establishment of RDT&E MILCON Projects Dashboard
This section requires the Under Secretary of Defense for Research and Engineering, in coordination with military department secretaries, to establish a central dashboard within one year. This dashboard will monitor and track data related to the planning, design, and execution of military construction projects for Research, Development, Test, and Evaluation (RDT&E) facilities across all military departments.
Supporters argue
Supporters argue this provision is crucial for modernizing DoD's infrastructure management by providing a single, comprehensive view of RDT&E facility projects, which will enhance strategic planning and resource allocation.
Critics contend
No specific opposition is typically raised against the concept of improved data visibility, though concerns might arise regarding the cost and complexity of implementation.
Tradeoffs
The primary tension is between the desire for enhanced oversight and the potential administrative burden and cost of developing and maintaining a new system.
Section 2(b)
Data and Functionality Requirements for the Dashboard
This section outlines the specific data points and functionalities the dashboard must include. It requires the use of existing financial management tools, display of facility location, manager, building number, plant replacement value, age, size, condition index, mission dependency index, programmed civil engineering projects and their value. It also mandates tracking unfunded facility requirements, summarizing real and non-real property data, using Real Property Unique Identifiers, and displaying data trends.
Section 2(e)
Dashboard Authority Termination
This provision stipulates that the authority to operate the dashboard established under this section will terminate on December 30, 2030. This sets a sunset date for the program, implying a review of its effectiveness before potential reauthorization.
Requires the Under Secretary of Defense for Research and Engineering to submit a recommendation to the Secretary of Defense on whether the dashboard's use should be continued, three years after enactment. Congress must be notified of this recommendation within 15 days.
Section 2(d)
Why it matters:This is standard legislative practice for including review mechanisms for new programs, often placed after the core operational details. It's not necessarily evasive but can be missed.
Case for: This provision ensures that the dashboard's utility is formally assessed after a period of operation, allowing for data-driven decisions on its future, rather than letting it continue indefinitely without evaluation.
Case against: Some might argue that a three-year window might be too short to fully assess the long-term benefits and integration of such a system, potentially leading to a premature recommendation.
Estimated impact: Ensures a formal review process for the dashboard's longevity and effectiveness.