1. EPICS: Engineering Projects in Community Service Habitat for Humanity Projects http://epics.ecn.purdue.edu/hfh

2. Habitat for Humanity Bringing families and communities in need together with volunteers and resources to build decent, affordable housing" - HFH International The HFH EPICS team tasks are to design systems and structures to minimize home construction and energy costs.

3. Habitat for Humanity HFH team works on the National, State, & Local Levels Multi-Institutional Projects  Notre Dame  Ohio State  Wisconsin-Madison

4. Purdue’s Habitat Team National Teams  Homeowner Surveys (NDB)  Construction Tutorial (Tutorials) Local Teams  Headquarters and Training Facility (HQ)  Restore Database Inventory Management (Restore)

5. Homeowner Surveys National Database Team Team Members Jeff Ross Noah Solomon John Horst Arthur Thompson

6. Problem Statement Problems for HFHI  No centralized survey administration and data collection system. Some local affiliates do their own surveying, but data is not shared.  There is no concrete quantitative data, currently, to show the benefits of the Habitat program to the community, both locally and nationally.  Homeowner information and responses must be securely collected, transferred, and analyzed to be in line with Habitat’s organizational mission.

7. Methodology Proposed Solution  Having a centralized secure server database for survey information and homeowner responses  Homeowner ID’s will be requested from the server but will be kept in paper records as to ensure the security of the information being recorded.  The web-based program will consist of three main parts:  A Survey Generator  Homeowner Response Collection\Input  Statistical Analysis

8. Technical Solution The current program relies on a single centralized database to hold the surveys, responses, and a list of questions and answers. It also relies on a web application to act as the front end to the database. HFHI standards are to use Microsoft products. We have adhered to HFHI standards. We are using ASP.net and MS SQL for this tool.

9. Tasks Completed  Beta Version Written (Spring 2004)  Reestablished communication (Fall 2004)  Design Documentation (Fall 2004)  Server up and running (Fall 2004)  Team has software (Fall 2004)  Documentation for all Previous Design Steps (Fall 2004) Outstanding  Version 1.0

10. Version 1.0 Pending approval from the project partner the following system will be implemented and delivered in Week 12 of Spring 2005:  User Management System (2 User classes)  National (1)  Local (~1700)  Each user level has different rights  National: Make Surveys, Enter Data, Export Data  Local: Data Entry

11. Next Steps Meeting with Professor Haurin at OSU Receive Feedback from IS dept at HFHI Start implementing design specs (Week 1-7) System Testing (8-12) Targeted Delivery Week 12 Spring 2005

12. Tutorials Team Team Members Aaron Rueth John Hostetler Hannah Mugford Richard Bowerman Construction Tutorials

13. Introduction Affiliates need a professional grade construction tutorial geared towards their volunteer base. Also wish to improve volunteer efficiency by giving them a solid background in their area of contribution.

14. Project Overview Construction Tutorials Project  Tutorial Template  Webpage  Reference Card  Tutorial Generator  Review Process  Feedback & Comment Forum  Revision and Update System

15. Progress Tutorial Template  Assess usability of current template  Testing the template on groups  Surveys to collect data University of Wisconsin-Madison  Four page on-site reference card  Currently six completed (Drywall, Siding, Trim, Interior Doors, Painting, Shingling)

16. Progress Tutorial Generator  Started this semester  ASP.NET and C#  Graphical User Interface  Information Entry  Currently working on HTML creation  Beta version complete in Spring 2005

17. Conclusion This semester, we came up with an overall view of where our project was headed and what was needed to delivery a project that could be continually revised and updated. The Tutorial Generator is the first phase in the automation of this project. After the completion of the generator, we will focus on the other systems involved in our project.

18. Headquarters and Training Facility Headquarters Team Team Members Jaime Alexander Dan Rorick Tim Chou Josh Copeland

19. Overview Problem: Habitat for Humanity of Greater Lafayette has outgrown their space. They need a place to continue construction during the winter months. Also, they would like to consolidate restore and offices. Goal: Our objective is to develop a feasibility report on a new training center/office building for the Greater Lafayette area Habitat for Humanity

20. Project Information Technical Progress:  Problem Identification  Specification Development Current Phase in Progress: Conceptual Design Documentation Completed in the EPICS design process:  Project Charter  Tech Appendix  Executive Summary

21. Project Planning Next Semester: Complete Conceptual Design  Decision Matrix of Requirements  Design Decision Table  Choose Design Approach Deliver Feasibility Report to HFH Lafayette, March 2005

22. Conclusion Team Headquarters is a few short weeks away from delivering the feasibility report to our Project Partner. Therefore, the objectives outlined are attainable and will be completed on time.

23. Restore Inventory Management Database Restore Team Team Members Garth Peterson Mitchell Harris Peter Morici

24. Goals Create a point of sale (POS) terminal  Must be easy to use  Suggest sale prices  Simple interface  As few steps as possible  Create invoice receipts  Accept donations  Inventory Search  Search by category  Financial report generator

25. Goals Build an inventory database  Linked to POS terminal  Access by HFH management at HQ (future project)

26. Current State of Operation Beginning Detailed Design phase  GUI Prototypes complete  Starting development of database

27. Progress Finished Problem Identification and Specification development Finishing Conceptual Design  Database structure  Program flowcharts Beginning Detailed Design phase  GUI Prototypes complete  Starting development of database  Small database prototypes

28. User Interface Layout Transactions Tab GUI Scanned Item shows up in Item Window with price Search option for the event the barcode falls off Manual entry for the event object can not be found Checkout button to finish transaction

29. User Interface Layout Donations Tab GUI Allows for the entry and categorizing of new donations Categorized list for easy entry of items Description of objects may be added in Description window

30. User Interface Layout Inventory Tab GUI Allows for a search of the inventory of the store Search by Category then Sub-Category

31. User Interface Layout Reports Tab GUI Generates financial reports Ability to search by any time period Ability to print report

32. Database Layout Category* Sub Category* General Item General Table* Item* Specific Item Specific Table* Item Specific Table* Item *Multiple Instances Database Structure

33. CVS and Eclipse Eclipse integrates CVS version control into the development environment. Both CVS and Eclipse are free / Open Source CVS provided by the CS department Eclipse on all ITAP computers

34. Java & MySQL Integration Java Connects to databases via JDBC MySQL is free and provides free driver for interfacing between the two. Advantages of JDBC Use standard SQL statements Standard Java interface

35. Database Connect Code

36. Database Query

37. Historic Centennial Neighborhood Association HCNA: Energy Efficiency in Historic Structures Ball State University: CERES

38. The Project Partner Historic Centennial Neighborhood Association  A group of homeowners determined to revitalize and stabilize the Lafayette neighborhood  Enlisted the help of EPICS for an engineering solution

39. The Team Gaurav Singhal  Mechanical Engineering Nikhil Thomas  Mechanical Engineering Bridget Webb  Civil Engineering

40. The Problem Historic Homes High Cost of Energy Bills

41. The Solution Custom built modeling package  Focus on historic residences  Takes into consideration the Secretary of the Interior’s Standards for Rehabilitation  Input specifics on house  Output guidelines on energy retrofits

42. The Objectives 1.What are the economic goals? 2.Are the historic homes inefficient? 3.If they are, how are they losing energy? 4.How can the efficiency be improved? 5.Will this change the historic value of the structure? 6.How can we inform the community of our findings?

43. The New Team New team Largest priority was creating a roadmap for future teams to follow  Division of team into subgroups  Aim to shorten time on learning curve for following teams

44. The Subgroups CARE  Community Awareness Research and Education DATA  Data Acquisition Testing and Analysis MAT  Modeling and Testing

45. CARE : This semester Acquisition of economic data  Existing economic data for individual homes and residences in the region  Attempted to find monetary goal  Contacts within Cinergy and Vectren

46. CARE : Future Semesters Act as liaison between community and EPICS team Educate community on energy efficiency issues Complete economic research Literary Research

47. DATA : This Semester Freshman Engineering house surveys  Created surveys of four historic houses  Researched guidelines for improvements  Compiled information generated from freshman  HOBO sensor research

48. DATA : Future Semesters Use sensors in a historic house Collect local climate data Construct data table for temperature and relative humidity Collaborate with CARE by providing engineering updates

49. MAT : This Semester Researched different modeling packages  Rem/Rate  Prism  EnergyPlus Web based tools Contacted modeling experts

50. MAT : Future Semesters Utilize data from DATA Test each modeling package for validity Create accurate models for historic houses Define assumptions and limitations for each existing modeling package Develop a custom modeling package

51. Deliverables Spring 2005  Informational packets for community  Recommendations on energy efficiency improvements to participating homeowners  Commencement of community seminars  Sensor and modeling data from first test house  Definition of economic goals

52. Summary Accomplished projects  Introductory collection of data  Creation of “roadmap” for future teams Ongoing projects  Definition of economic aims  Collection of house and local data  Testing of existing modeling packages Final Project  Creation of custom modeling package

53. Discussion Any Questions Thank you