SAN JOAQUIN RIVER Dissolved Oxygen Total Maximum Daily Load Stakeholder Process

Next Technical Committee Meeting: August 26, 9 - noon DWR, 3251 S Street, Sacramento (large conference room)

1. Database Management
   1. Goals
      1. All historic and current physical and biological data needed to analyze the TMDL and alternative solutions are compiled and organized in an easy-to-find, easy-to-use, updateable manner through a single database that is available to users in perpetuity and benefits an adaptive management planning and implementation program.
      2. All needed data is uniformly formatted and accompanied with the metadata so that it meets user needs and is broadly usable in different analytical tools. Metadata includes georeferencing information.
      3. Data that could help in immediate and long term understanding and managing the system is made accessible in a near real time manner.
      4. The database clarifies whether and how data has gone through a QA/QC process. Researchers are able to (and do) comment on the quality of the data so that a process of continual improvement in knowledge about the data can occur.
      5. The quality and accessibility of the data and database reduces short and long-term costs to the regulated and regulators.
      6. The quality of the database helps build trust in the consensus process and in the ultimate solutions enacted.
   2. IEP's Database
      1. The Technical Committee decided to use the IEP database to manage and store current, future and historical data needed in the TMDL and Adaptive Management programs.
      2. Karl Jacob (IEP) and Jones and Stokes staff will meet the week of August 16 to develop a work plan for data management that meets the above goals. This work plan will be presented at the next Technical Committee meeting (August 26).
      3. Some issues that the work plan will address include:
         1. Who will be responsible for collecting, storing, and checking quality of data
         2. How will historic data be made accessible and meet the goals above.
         3. How to store and make accessible time series data.
         4. How to get NPDES and other current data into the IEP system as soon as possible.
         5. The budget, who does what and where and when funds will come to pay for it.
         6. What should be done with mapping data.
2. Analytical Tools
   1. Kevin will redraft a set of goals for the analytical tools and present them at a future technical committee.
   2. Analytical tools as part of TMDL and December 2002 Objectives
      1. Regional Board staff will clarify what they think the stakeholder process should be developing in the area of analytical tools. It is assumed that the implementation plan will be an adaptive management plan and will need analytical tools for decades of ongoing improvements.
   3. USEPA BASINS and Similar Tools
      1. This public domain software could be useful as a tool to develop the TMDL. There were numerous positives and negatives mentioned about the tool. It was determined that it is not necessary at this time to choose which tool (USEPA BASINS, Systech's Watershed Analysis Risk Management - WARM, or another) is used. This can wait until year 2.
   4. The next meeting on Database Management is scheduled for August 26 Technical Committee meeting.