1. Redefinition of Scope Presenter: Darrin Polhemus 1

2. 2 Recommendation 1: Reduce Project’s Scope   An explicit definition of CIWQS’ core regulatory functions has been established - DONE   The Steering Committee has reviewed and approved this definition - DONE   All members of the CIWQS team understand and agree with the redefined scope - DONE

3. 3 Definition Also Supported in Other Actions   Items cut from scope   Co-management of CIWQS and PCS/ICIS-NPDES together   Principle Operating Directives   Agency Information Management Strategy

4. 4 CIWQS Definition and Scope   General functionality provided by CIWQS   Water Board Programs utilizing CIWQS   Receive, manage and provide data submitted by regulated entities for the following…   External interfaces with other systems

5. 5 CIWQS Definition and Scope   General functionality provided by CIWQS: Permit and Order tracking (Party/Place/Regulatory Measure) Track inspections Track self-monitoring reports Manage violations and enforcement activities Reporting of regulatory information both internally and externally, including to the public

6. 6 CIWQS Definition and Scope   Water Board Programs utilizing CIWQS: NPDES (discharges to surface waters) WDR (discharges to land or non-federal water) Landfills Storm Water Water Rights (eWRIMS) Irrigated Lands [for enforcement and billing only]

7. 7 CIWQS Definition and Scope   Receive, manage and provide data submitted by regulated entities for the following: Online reporting of sanitary sewer overflows (SSO) Online submittal of Storm Water annual reports (SWARM) Online submittal of NPDES self-monitoring reports (eSMR) Online enrollment in Storm Water General Permits (SWPAP) [under development, will replace SWARM] Online submittal of water use data [new functionality; under development]

8. 8 CIWQS Definition and Scope   External interfaces with other systems: Water Boards billing system (Automated Fee Billing System (AFBS) or successor) U.S. EPA’s NPDES tracking system (PCS/ICIS) [under consideration] Electronic Content Management [in pilot testing]

9. 9 Modules Since Last Review   Sanitary Sewer Overflow (SSO) module Online reporting of sanitary sewer spills   Water Rights Information Management System (eWRIMS) Replaced old water rights system Has large GIS component Connects at Party and Place tables

10. 10 Systems No Longer in CIWQS Scope   Geotracker Remain separate system Soliciting software-as-a-service vendor   SWAMP Upgrading from MS Access to MS SQL Support California Data Exchange Network (CEDEN) Utilize California Water Quality Monitoring Council to provide guidance on new system parameters

11. 11 Systems No Longer in CIWQS Scope   GAMA GAMA Public Advisory Committee requested functionality Soliciting software-as-a-service vendor   GeoWBS Some functionality such as combined listing be added to existing system Long range plans undetermined

12. 12 CIWQS and PCS/ICIS- NPDES Can two systems work together and complement each other?

13. 13 CIWQS and PCS/ICIS-NPDES   Both systems have to exist – have functionality that is unique to each CIWQS: billing, NPDES/WDR overlap, Self- monitoring reporting (SMR), mandated reporting [WC 13385(o)], etc… PCS/ICISN-PDES:Discharger Monitoring Reporting (DMR), automated determination of compliance, compilation of QNCR, etc…

14. 14 CIWQS and PCS/ICIS-NPDES   Approaches CIWQS feeds PCS/ICIS-NDES – tried that Modify PCS/ICIS-NDES to CA needs – won’t happen Co-manage both systems together to exploit strengths of each – common middle ground

15. 15 CIWQS and PCS/ICIS-NPDES   Water Board Approach Commit to managing information in PCS/ICIS- NDES Will look at small defined data flows, both ways between systems, when able, but until then will make sure data is entered into PCS/ICIS-NDES Incorporate PCS/ICIS-NDES reporting into program management

16. 16 Principle Operating Directives Rules to live by!

17. 17 Principle Operating Directives   Purpose of CIWQS – Primarily a regulatory information management system to: Manage business processes Work in conjunction with other data systems Inform decisions Provide accountability   Secondary role is for automation

18. 18 Principle Operating Directives   Expansion of CIWQS Only add new modules when existing needs met The need for new module has been identified and justified Resources for the new module are available and have been adequately allocated There is common data and functionality between new module and CIWQS

19. 19 Agency Information Management Strategy Changing the approach so that this is not an oxymoron.

20. 20 Agency Information Management Strategy – The Old One CIWQS as an enterprise wide system (solution) CIWQS as an enterprise wide system (solution) Encompass all Water Board programs: surface water, ground water, planning, etc. Encompass all Water Board programs: surface water, ground water, planning, etc. All programs share information in same data structure All programs share information in same data structure System usage promotes (requires) changes in programs System usage promotes (requires) changes in programs Centralize Information Technology Centralize Information Technology Strong IT in control of development Strong IT in control of development Bring systems together – single technology solution Bring systems together – single technology solution 20

21. 21   Business needs drive strategy Programs in direct charge of projects   Have different and distinct groups of users with different needs and skill levels General Public, Legislature, dischargers, internal users   Enterprise Portfolio Management Multiple systems, meeting a multitude of needs, working together (federated?) Agency Information Management Strategy – The New One

22. 22 Agency Information Management Strategy – The New One   Listing of Legislative and Administrative Mandates First time comprehensive list included in strategy   List of projects and process for Water Boards Details underway and prospective Defines program group responsible for managing

23. 23 Questions? Attachments: CIWQS Definition Principle Operating Directives