 Hello everyone, I'm Doug Chalmers with the Stockholm Environment Institute, and I'm here to talk to you today about the ERIMS Analyzer, which is a tool I developed with the State Water Resources Control Board to look at water rights data. In this presentation, I'll be talking about what is the ERIMS Analyzer, what kinds of questions can it answer, and then I'll be giving a walkthrough tour in Excel. So what is the ERIMS Analyzer? It is an Excel tool with VBA coding in the background to process water rights data. And this water rights data, as input to the tool, comes from the ERIMS Water Rights Database, which is found online and available to the public, and it's where the State Water Board stores its electronic water rights from across the state. ERIMS Analyzer takes this information from the ERIMS database, and it processes it to form monthly use estimates for each water right in Excel. So what kinds of questions can the ERIMS Analyzer answer? You can use the tool to explore things like what are the monthly diversions in my watershed, what do the user reports show each year, which water rights have data discrepancies, and you could use the Excel filters to look at any number of custom queries like how many water rights show blank in my watershed. So enough about talking about it, let's check it out. So the ERIMS Analyzer comes packaged in a folder with a readme word file, as well as a logic tree file, which show how the algorithms are calculated. Most of the action goes on in this main ERIMS Analyzer Excel file. And in this Excel file, it has its own readme. The sheets are nicely laid out in order to help guide the user. Each sheet has plenty of documentation to help guide what's going on. And the user interacts with the spreadsheet in order to use the tool. So to use the tool, you import the data, which was downloaded from that ERIMS database, and then you process the data to produce calculations like the diverted total estimates. And the diverted total are monthly estimates for each water right of when is the water actually drawn and diverted out of the stream. And also calculated is amount used, which is when is the water actually applied and used. And both the diverted total and the amount used are calculated because for water rates which have storage, they may divert the water in the winter and then actually use it in the summer. And the diverted total and amount used are calculated in what's called a reported water use scenario, which looks at what use was reported to the board in the past. In addition to the reported scenario, there's a permitted water use scenario which looks at what is the maximum amount allowed according to the water rate. And then in addition to the estimates, the tool compiles application info associated with the water rates. And there's also a handy water use report matrix, which shows the amounts reported to the board for each year. So you could look at are the reports changing through time and are certain water rates even reporting at all. The tool will also flag any applications which have data discrepancies, which the user can go into the worksheets and semi-automatically resolve these data discrepancies to produce more accurate water use estimates since the data in the database is often incomplete. At which time there's this watershed summary report feature, which gives you kind of a high level big picture of what's going on in the watershed so you can easily and quickly follow. You can print this summary report to a PDF and it looks at things like the totals for the scenarios, the beneficial uses, owners with high diversions as well as HUC-12s. And finally, you can export time series CSVs so you can use them in a model of your choice. SEI has done this with projects using wheat models. So if you like what you see and you're interested in accessing the ERAMS analyzer, the best way to do so is to either contact myself, Doug Chalmers or Raja Hassan at the State Water Board. And with that, I just want to say thank you for listening and thanks to folks in the State Water Board as well as colleagues at SEI for supporting this effort. And at this time I'll take your questions. Thank you so much.