CIWQS – eSMR Redesign Presenter: Presenter: Amy Tong, Darrin Polhemus and

Akin Babatola 11

22

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

33

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

44

eSMR user group and project team

Paul YaoOracle DBA

John GinnApplication Tester

Rueen- Fang WangData Modeler

James MiersOracle DBA

Rassam ZarghamiSWRCB SME

Mike PaulucciDischarger SME

Russ ColbyRB4 SME

Jack PriceRB4 SME

Alex CarlosRB4 SME

John CarmonaRB7 SME

David LaCaroRB3 SME

Susan BremserDischarger SME

Akin BabatolaDischarger SME

Joy CastaingDischarger SME

Patrick IngramDischarger SME

Dan PierceDischarger SME

Kay YamamotoDischarger SME

Rachel Van ExelDischarger SME

Edward FilodolflaDischarger SME

Valerie HouselDischarger SME

Mike TrouchonDischarger SME

Jason SinklerDischarger SME

Dan JacksonDischarger SME

Imam MohammedDischarger SME

Larry KerriganDischarger SME

Amy TongTechnical Sponsor

Darrin PolhemusProject Program Sponsor

Don SwidenSWRCB SME

Jon BishopProject Executive Sponsor

Francisco ChiangeSMR

Application Developer

Hoang NguyeneSMR

Application Developer

Ron RobinetteProject Manager

Discharger Steering Committee

Sandy CheekRB3 SME

Diane O’DonohueDischarger SME

55

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

66

Re-evaluate System Requirementscont’d

Identified system/process issues and “bottle neck”, and evaluated levels of submittals Automatic Violation creation

Error Check

Permit Coding

77

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

88

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

99

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

1010

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

1111

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

1212

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

1313

eSMR2 Project Schedule

Begin Re-evaluation of

system

De

ce

mb

er

20

07

Design Begins

Fe

bru

ary

20

08 Ju

ly 2

00

8

Complete Design

Completed Tasks

Planned Tasks

No

ve

mb

er

20

07

Fe

bru

ary

20

08

Fe

bru

ary

20

08

ProductionRoll-out

Alpha Testing (Prototype)

Beta Testing

Ma

y 2

00

8

Decision on proposed approach Develop usability

testing plan

Ap

ril

20

08

Ja

nu

ary

20

08

Ma

rch

20

08

Formed eSMR UserGroup Team Provide screen

mockups

Develop implementation plan for Level 2

Ma

rch

20

08

Ma

rch

20

08

System ProgrammingBegins

1414

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

1515

Questions

1616

eSMR2 Mockups Demo By

Ron Robinette, Akin Babatola,

James Miers and Francisco Chiang