1<!doctype html> 2<html lang="en"> 3<head> 4 <meta charset="utf-8"> 5 <meta name="viewport" content="width=device-width, initial-scale=1.0"> 6 7 <!-- Google tag (gtag.js) -->
vendor: 69 bytes, lines 7-8
7 8 <script async src="https://www.googletagmanager.com/gtag/js?id=
8G-QYQBXTX8Z7
vendor: 65 bytes, lines 8-9
8" type="3b2b70fa6610fd4e25e5d49b-text/javascript"></script> 9
9<script type="3b2b70fa6610fd4e25e5d49b-text/javascript"> 10
vendor: 159 bytes, lines 10-14
10window.dataLayer = window.dataLayer || []; 11 function gtag() { dataLayer.push(arguments); } 12 gtag('js', new Date()); 13 14 gtag('config', '
14G-QYQBXTX8Z7
vendor: 9 bytes, lines 14-15
14'); 15
15</script>
15 16 17 <title>Executive Directorâs Message, Summer 2026 | Susquehanna River Basin Commission (SRBC)</title> 18 19 <meta name="author" content="Susquehanna River Basin Commission" /> 20 <meta name="date" content="August 13, 2026" /> 21 <meta name="description" content="Read the Summer 2026 Executive Directorâs Message from the Susquehanna River Basin Commission (SRBC), with reflections on leadership, water resource management, and the future of the Susquehanna River Basin."> 22 <meta name="keywords" content="Susquehanna River Basin Commission, SRBC, Executive Director, message, water management, environmental policy, quarterly update, Susquehanna River Basin"> 23 24 <!-- Open Graph / Social Sharing --> 25 <meta property="og:title" content="Executive Directorâs Message | Susquehanna River Basin Commission"> 26 <meta property="og:description" content="Quarterly updates from SRBCâs Executive Director on programs, priorities, and the state of the Susquehanna River Basin."> 27 <meta property="og:type" content="article"> 28 <meta property="og:url" content="https://www.srbc.gov/welcome.html"> 29 <meta property="og:image" content="http://www.srbc.gov/images/andrew-dehoff-2018-fall-newsletter.jpg"> 30 <meta property="og:site_name" content="Susquehanna River Basin Commission"> 31 32 <!-- Twitter Card --> 33 <meta name="twitter:card" content="summary_large_image"> 34 <meta name="twitter:title" content="Executive Directorâs Message | SRBC"> 35 <meta name="twitter:description" content="Quarterly message from SRBCâs Executive Director with updates on water management and policy."> 36 <meta name="twitter:image" content="http://www.srbc.gov/images/andrew-dehoff-2018-fall-newsletter.jpg"> 37 38 <link rel="canonical" href="https://www.srbc.gov/welcome.html"> 39 40 <link rel='stylesheet' id='font-awesome-css' href='https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css?ver=4.7.0' type='text/css' media='all' /> 41 <link href="https://fonts.googleapis.com/css?family=Cormorant:300i|Muli:400,400i,700,700i" rel="stylesheet"> 42 43 <!--main style sheet file--> 44 <link href="css/srbc.css" rel="stylesheet" type="text/css" /> 45 46 <!--jQuery--> 47
47<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.7.1/jquery.min.js" integrity="sha512-v2CJ7UaYy4JwqLDIrZUI/4hqeoQieOmAZNXBeQyjo21dadnwR+8ZaIJVT8EE2iyI61OV8e6M8PP2/4hpQINQ/g==" crossorigin="anonymous" referrerpolicy="no-referrer" type="3b2b70fa6610fd4e25e5d49b-text/javascript"> 48 </script>
48 49 <!--this include the header, footer and page bottom--> 50
50<script src="scripts/jquery-include.js" type="3b2b70fa6610fd4e25e5d49b-text/javascript"></script>
50 51 52</head> 53<body> 54 <div id="wrapper"> 55 <div id="header"> 56 57 </div> 58 <div class="accent slim"></div> 59 <main id="content"> 60 <nav aria-label="Breadcrumb"> 61 <ol class="breadcrumbs-accessible"> 62 <li><a href="index.html">Home</a></li> 63 <li aria-current="page">Welcome</li> 64 </ol> 65 </nav> 66 <h1>Executive Director's Message, Summer 2026</h1> 67 <h2> 68 Navigating Transparency in Changing Waters 69 70 </h2> 71 <figure class="quarter"> 72 <img src="images/andrew-dehoff-executive-directors-message.jpg" 73 alt="Andrew D. Dehoff, Executive Director" /> 74 <figcaption>Andrew D. Dehoff, P.E. <br /> Executive Director</figcaption> 75 </figure> 76 <p> 77 In the interest of remaining responsive to the evolving landscape surrounding 78 <a href="regulatory/data-centers/">data centers</a>, 79 we recently 80 made a determination that will affect the public comment process for certain projects in the Susquehanna 81 River Basin. We realize public interest will only continue to grow as data center development advances 82 in our watershed. 83 </p> 84 <p> 85 At the same time, we are beginning to notice an increasing number of data center 86 developers choosing designs that use water provided directly from existing public water supplies 87 rather than pulling new water from rivers and streams or drilling new groundwater wells. Cases like 88 these would not require a withdrawal approval from us because the water theyâre using is already 89 regulated through the public water supply system. We already account for that water through the public 90 water supplierâs existing withdrawal approval. 91 </p> 92 <p> 93 However, this approach does require our approval for the consumptive use of water (water used but not 94 returned to the basin) if the volume being used by the data center exceeds our threshold of 20,000 95 gallons per day over a 30-day average. Consumptive uses of water solely supplied by public water 96 supply, stormwater, wastewater, or other reused or recycled water may receive a Commission approval 97 known as an Approval by Rule, type (e), or âABR(e)â. An ABR(e) is a type of general permit, and this 98 process has been in place since 2007 for all large water users in the basin. 99 </p> 100 <p> 101 ABR(e) permits can be issued by the Executive Director after a staff review of the application. The 102 process is simpler than a withdrawal application, because remember, the water quantity has already been 103 thoroughly scientifically reviewed and approved at the withdrawal source, and determined to be 104 sustainable for the public water supplier. The public water supplier has the discretion and 105 responsibility of managing their allocation of water within approved limits. 106 </p> 107 <p> 108 This brings me back around to the determination I mentioned at the top of this message. According to 109 our 110 <a href="https://www.ecfr.gov/current/title-18/chapter-VIII" target="_blank">Code of Federal Regulations</a> 111 , ABR(e) applications are subject to a written comment period. But 112 applications for this type of project are not required to be included in the Commissionâs quarterly 113 public hearing process. Given the heightened public interest and scrutiny involving data center 114 development, under my authority as Executive Director of the SRBC, the Commission will now require any 115 application for an ABR(e) filed for a data center to be included and subject to a quarterly public 116 hearing before any determination is rendered. 117 </p> 118 <p> 119 The Commission has always had a very robust <a href="regulatory/public-participation/">public participation</a> and comment process. You could always 120 submit written comments on an ABR(e) application. We are simply raising awareness of this opportunity 121 and offering the additional option to orally submit as well through the formal hearing process for 122 proposed consumptive water use by data centers using a public water supply. A more detailed
123 <a href="regulatory/data-centers/docs/ABR(e)-determination.pdf" target="_blank">explanation of this determination</a> 124 as well as an 125 <a href="regulatory/data-centers/docs/ABR(e)-frequently-asked-questions.pdf" target="_blank"> FAQ on ABR(e) projects</a> 126 can be found on our website. 127 </p> 128 129 <p>Best regards,<br />Andrew D. Dehoff, P.E.<br>Executive Director</p> 130 </main> 131 <div id="footer"> 132 </div> 133 <div id="bottom"> 134 </div> 135 <div class="clear"></div> 136 </div> 137
137<script type="3b2b70fa6610fd4e25e5d49b-text/javascript"> 138 $('.toggle').click(function () { 139 $(this).toggleClass('open'); 140 }); 141 </script>
141 142 <!-- Put the following javascript before the closing tag. --> 143
143<script type="3b2b70fa6610fd4e25e5d49b-text/javascript"> 144 (function () { 145 var cx = '014275456448856624016:2nhssjfy6hc'; // Insert your own Custom Search engine ID here 146 var gcse = document.createElement('script'); gcse.type = 'text/javascript'; gcse.async = true; 147 gcse.src = 'https://cse.google.com/cse.js?cx=' + cx; 148 var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(gcse, s); 149 })(); 150 </script>
vendor: 144 bytes, lines 150-151
150 151<script src="/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js" data-cf-settings="3b2b70fa6610fd4e25e5d49b-|49" defer></script>
151<script type="module" src="https://static.cloudflareinsights.com/beacon.min.js/v31edd6df95cf4e85bb4c19e7a9bdbcba1788362987495" integrity="sha512-iIg7k2xntmwu6/uSb5tpc/hySgZc4eoL31yB29W6tJFo2akwjPWcEqnCEdJvGexCL0KEQwVYv5BlowfhVz26hg==" data-cf-beacon='{"version":"2024.11.0","token":"42c4b29eb5364479b2347c43e8efe96d","spa":2}' crossorigin="anonymous"></script>
151 152</body> 153</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.