1. Presenter: CIWQS – eSMR Redesign Presenter: Amy Tong, Darrin Polhemus and Akin Babatola 1

2. 2 Topics   What has been done Formed a new eSMR user group and project team Re-evaluated system and its requirements Proposed a new design (deploy system in phases/levels) Provided screens, reports, and special tools mockups Developed a formal usability test plan Developed an implementation plan for Level 2

3. 3 Topics   What is next System programming Conduct usability testing Outreach and training planning System alpha and beta testing, user acceptance System rollout Post system implementation evaluation   Looking ahead for next requirement (level 2.5) – data flow to EPA system

4. 4 eSMR user group and project team

5. 5 Re-evaluate System Requirements  Re-analyzed permit submittal process and business flow - walk through a life of a eSMR permit  Reviewed existing system  Mapped existing system to process

6. 6 Re-evaluate System Requirements cont’d  Identified system/process issues and “bottle neck”, and evaluated levels of submittals Automatic Violation creation Error Check Permit Coding

7. 7 A new design – phased approach   Leveraged SWIM II design, combined with current requirements   Phased approach: Level 1 - Report Verification: Receive report electronically Level 2* - Usable Data: Complete data upload in an usable format with report timeliness check Level 3 – Sampling Advisory Compliance Checking: Report contents are logically compared to monitoring requirements (primarily effluent and receiving water monitoring) Level 4 – Complete Advisory Compliance Checking: Report contents are logically compared to preset thresholds to determine compliance

8. 8 A new design – phased approach (cont’d)   Proposed Level 2 design with an implementation date of July 2008 Discharger submits monitoring data in usable* format (raw data and calculated summary data) Dischargers self enters violations What they entered is what shows on report Reports and Analytical tools for data viewing and querying for both Dischargers and RB case workers *Usable=able to be analyzed by State and Regional Board staff

9. 9 Pros of Level 2   No system generated Violations   No barrier for data submission due to system inaccuracy (Error check issues)   No barrier to start data submission due to lack of resource to code permit (Permit coding by RB)   What discharger entered is what shows on public report   Analytical Tools for data analysis and data extraction after data submission

10. 10 Cons of Level 2   Discharger has to enter the Violations according to cover letter   RB case worker has to manually review Violation entries   The system does not do compliance check so Discharger and RBs have to do compliance check manually   Have to wait for Level 3 and 4 in order to have limited and complete compliance check capability

11. 11 Schedule   Level 2 – Usable data submission - July 2008   Level 2.5 – to address DMR dataflow to EPA system – Fall to Winter 2008 (EPA system is not ready until Fall of 2008)   Level 3 - Sampling Advisory Compliance Checking monitoring data – pending funding availability   Level 4 – Complete Advisory Compliance Checking with complete permit coding – pending funding availability   Current eSMR system will continue to function in maintenance mode

12. 12 Screens, Reports, and Analytical Tools mock ups – Level 2   Map screens and data to requirements   Solicit comments on mock ups   Document comments on Issue Tracker and evaluation sheets   Evaluate other systems to get ideas   Develop usability testing plan

13. 13 eSMR 2 Project Schedule Begin Re- evaluation of system December 2007 Design Begins February 2008 July 2008 Complete Design Completed Tasks Planned Tasks November 2007 February 2008 Production Roll-out Alpha Testing (Prototype) Beta Testing May 2008 Decision on proposed approach Develop usability testing plan April 2008 January 2008 March 2008 Formed eSMR User Group Team Provide screen mockups Develop implementation plan for Level 2 March 2008 System Programming Begins

14. 14 Next Step   Level 2 implementation System programming Conduct usability testing Schedule and Resources Communication, Outreach, and Training System alpha and beta testing and acceptance System/requirements cross reference (on-going): data, data quality, functionality, and data outputs System roll out and post implement evaluation   Continue design of Level 2.5

15. 15 Questions

16. 16 eSMR2 Mockups Demo By Ron Robinette, Akin Babatola, James Miers and Francisco Chiang