1. Biosolid Project Presentation Dec 12, 2005 The Team Programmers Dan McAfee Chris Middleton Erik Rottier John Stephen Clients Dr Shunfu Hu Dr Jianpeng Zhou Management Dr Ehlmann

2. Overview Introduction Requirements Project Plan Design Demonstration Retrospective

3. Introduction Wastewater Treatment Facilities Generate Biosolid Waste Waste Information Collection –Guided by Federal Regulations (USEPA 40 Part 503) –Current systems Paper Forms Limited Standalone Computer Systems Geographically Dispersed Sites Limited Systems Analysis –Manual compilation of raw data Paper Limited Computer Systems –No ability to view data in relation to Source Geography Destination Geography 1st Goal: Automate Wastewater Biosolid Information Collection & Reporting

4. Introduction Continued… Geographical Information System (GIS) –Linking spatial (geography/maps) with Non-spatial (attribute data - e.g. soil composition, dominant vegetation) 2 nd Goal: Demonstrate Viewability of Submitted Data Graphically with GIS Analysis Functionality Proof of Concept System from two goals: WBIMS Wastewater Biosolids Information Management System

5. Team Organization Organized to Sub Projects –Primary/Alternate SME Roles Coder/Reader Resource Balancing/Backup Additional Roles –Project Leader Project Direction/Scheduling Primary Client/Management Contact –Web Administrator Manages Team Web Site Meeting Minutes Erik Rottier BDMS (Primary) Front End (Alt) Erik Rottier BDMS (Primary) Front End (Alt) John Stephen [Web Master] Front End (Primary) BDMS (Alt) John Stephen [Web Master] Front End (Primary) BDMS (Alt) Clients Dr Shunfu Hu Dr Jianpeng Zhou Clients Dr Shunfu Hu Dr Jianpeng Zhou Dan McAfee [Project Leader] Database (Primary) ArcGIS (Alt) Dan McAfee [Project Leader] Database (Primary) ArcGIS (Alt) Clients Dr Shunfu Hu Dr Jianpeng Zhou Management Dr Bryon Ehlmann Chris Middleton ArcGIS (Primary) Database (Alt) Chris Middleton GIS (Primary) Database (Alt)

6. Biosolid Requirements Functional Requirements Non-Functional Requirements Use Case Model

7. Functional Requirements Universal Access Credential Verification Ability to Input Biosolid Information Some Analysis Capability Ability to display : –Buildings –Topology –Land Application Site

8. Non-Functional Requirements Usability - keep typing to a minimum, Users Manual Reliability - automatic reboot upon failure Performance - 250 concurrent users Supportability - EPA office, federal system, other OS support Implementation –Biosolids Data Management System (BDMS) EPA approved system Mandated by the client for wholesale inclusion into this project Will provide the ‘SubmitInfo’ structure to the new system Drafts adherence from those who presently use the BDMS –Graphic Display Capability Started with ArcGIS and ArcIMS Migrated to GoogleMaps Supports demonstration capabilities to IEPA representatives –Interface – Web Access

9. Requirements Modeling Use Case Model Graphical/ Biosolid System Treatment Plant Personnel EPA Personnel All Others SubmitInfo ViewInfo 1 1 1 1 2 2 2 2 3 3 3 3 3 3 BDMS System GIS System Includes Login

10. Biosolid Plan Software Lifecycle Testing Deployment Risk Management

11. Software Lifecycle Waterfall Model with Sub Projects –Team Organization / Sub Project Focus –Ideal for Concurrent Development –Iterative Lifecycle Not Appropriate Due to Larger System Size / Limited Time

12. 3 Phases of Testing Unit Testing –Sub Project Dependent –Primary Coder / Coder/Reader Integration Testing –Between Sub Projects –Sub Project Primary SME Coordinated System Testing –Single User Functionality Testing

13. Deployment During Project –Capture Configurations System Component Configuration (IIS, Microsoft SQL Server) Front End Configuration Google Map Configuration BDMS Configuration Prior To System Testing –Create Software Installation Documentation Document System Pre-Requisites (e.g. IIS Web Server) Primary Configuration of Custom Software Validate in Testing At Close of Project –Transfer All Documentation to Clients –Clients Have Technical Skills and Resources –Oversee Successful Deployment to Client Workstation

14. Risk Management Table Early acquisition; Configuration Management; Schedule Changes to Accommodate LowHardware/Software Issues Re-assignment of work; reduce feature set; managerial guidance ModeratePersonnel Issues Further analysis; adherence to specificationsModerateFeature Creep Include time buffers; reduce feature setModerateOverly Optimistic Schedule Review and re-designHigh Inadequate Design or Base Systems Seek guidance; reduce feature set; revert to known technologies HighUpfront Learning Curve Risk Resolution Risk Potential Potential Risk

15. Biosolid Design Overview Subsystem Decomposition HW/SW Mappings Persistent Data Management Data Mapping/Map

16. Design Overview GeographicallyDistributed Users Operating System - ( Windows XP Web Server DBMS System GIS Server System S Q L / S t o r e d P r o c s INTERNET EPA Personnel Wastewater Treatment Facility Personnel General Public(e.g.Public Health, Researchers,Interested People) Web Browser WBIMS Web App Server Web Browser High-level approach to implementing WBIMS – Proof-of-concept Prototype – Single Hardware Server ▪ Web Server, DBMS, GIS, & WBIMS custom software Database (GIS & Biosolid Data) Wastewater Biosolids Information Management System (WBIMS)

17. System Architecture Style –3-Tier System Architecture A Logical vs. Physical Distinction –User Services (1) »Client script & Html served up by ASP.Net –Business Services (2) »Code-behind (C#) & GIS scripting –Data Services (3) »Stored Procedures, SQL –4 Primary Functional Areas Web Front End “Submit Info” Sub-system (BDMS) “View Info” Sub-system (GIS) Database Back End Design Overview Continued…

19. Hardware/Software Mapping Routing Subsystem runs on the Server Biosolid Login & Main Menu runs on the Web Server BDMS System runs on the Web Server GIS System on the Web Server –Access to Google via API. Consolidated Database is housed on the SQL Server

20. Persistent Data Management This project uses a relational database for all persistent data instantiation. BDMS system uses forms with fields that can save data to the database via the DBMS. Each data access system will be shifting from direct data access (Microsoft Access) to an indirect access via Microsoft SQL Server DBMS. –This layering will protect the data from concurrent users, system shutdowns and other various data risk activities.

21. Data Mapping Sub System Area # of HTML Pages to Create BDMS Screen Shot Name Tied To BDMS Table Main BDMS Screen1 BDMSNone General Facility Information4 gen_fac General Facility Information (Add) Page 1 gen_fac General Facility Information (Add) Page 2 gen_fac General Facility Information (Add) Page 3 gen_fac Contract Haulers2 Contract Appliers/Haulershauler Contract Appliers/Haulers (Add) hauler Biosolid Treatment Provided1 Biosolids Treatment Provided (Add) sludge Final Disposal3 Final Use/Disposal Practices (Add) Page 1 disposal Final Use/Disposal Practices (Add) Page 2 disposal Final Use/Disposal Practices (Add) Page 3 disposal

22. Data Mapping Continued… Sub System Area # of HTML Pages to Create BDMS Screen Shot Name Tied To BDMS Table Site Information9 Land Application Site Information site Land Application Site Information (Add) Page 1 site Save ConfirmationNone Crop Nitrogen Calculationsite_crop Crops and Nitrogen Recommendations site_crop Land Application Site Information (Add) Page 2 site Individual Load Trackingload_tracking Land Application Site Information (Add) Page 3 site Land Application Site Information (Add) Page 4 site Monitor Data Summary3 Monitoring Data Summarymonitor Monitoring Data Summary (Add) Page 1 monitor Monitoring Data Summary (Add) Page 2 monitor Individual Pollution Results3 Individual Pollutant Resultsmon_trk Individual Pollutant Results (Add) mon_trk Pollutant ResultsNone Pathogen Reduction and Vector Attraction Reduction (VAR)2 Pathogen Reduction and VARaltmethd Pathogen Reduction and VAR (Add) altmethd

23. Data Map

24. Project Demonstration

25. Retrospective The Biosold project went well. –Design was solid. –Schedule had enough built-in time to absorb delays. –We were able to interface BDMS with Googlemaps –We added statistical charts needed by Clients –Testing has been catching areas needing improvement Some Hurdles to Overcome: –Non-functional requirement to use ArcGIS/ArcIMS ArcGIS works Great ArgIMS works Great ArcIMS with ArcGIS doesn’t work at all – needed –Project Interference Employers over employing Personal Issues

26. Questions?