EPICS Lafayette Crisis Center

1
EPICS Lafayette Crisis Center

• Design Review
• Fall 2004

2
Lafayette Crisis Center

• Non-profit human service organization
• Round-the-clock crisis intervention, suicide
  prevention, and information and referral
• Confidential, free and available by phone or in
  person 24 hours a day, 365 days a year

3
LCC Team Organization
Advisor Tim Strueh Co-Advisor Heather
Connell Team TA Gary Lee
4
Current Projects

• Community Information Kiosk
• Software
• Hardware
• Scheduling Software

5
Kiosk Software
6
Objectives

• Implement auto-update of Kiosk Database
• Documentation

7
Background Info

• Two Major Functions
• Detection and Recovery of PC Lockup
• Intelligent Phone Connection Management
• Reasons for Building
• Cost Cheaper than any commercial product
• Expandable Capable of growing to meet future
  needs

8
Design

• Windows 2000
• Java 1.4.2
• Tomcat 5
• All information passed to current page
• Print and Call natively in Java
• Phone number checking

9
Demonstration
10
The Kiosk Auto-Update System

• Need a more user-friendly way of updating the
  database on each individual kiosk before multiple
  kiosks are deployed to community
• Also could be used to update kiosk software as it
  is worked on

11
Auto-Update Block Diagram
As the LCC makes update to their database
they ftp these changes onto the server
FTP Server (LCC account set up on
shay.ecn.purdue.edu)
Individual Kiosks ftp changed server files off
the server once a month
Kiosk
Kiosk
Kiosk
Kiosk
Kiosk
Lccserver
12
Progress

• Added last updated field to info.html
• Acquired ECN username for auto-update
• Wrote scripts to auto-update lccserver.ecn.purdue.
  edu
• Began process of acquiring dial-up internet
  connections for kiosks

13
Kiosk Hardware
14
Objectives

• Redesign watchdog to move AC off of DC PCB
• Implement and test phone functionality
• Repairing broken Lincoln Center kiosk
• Finalize design of Control Box

15
Control Box Motivation

• Cost Cheaper than any commercial product
• Programmable We can program it to do virtually
  anything
• Expandable Capable of growing to meet future
  needs

16
Control Box Purpose

• Detection and recovery of PC lockup
• Intelligent phone connection management

17
Current Control Box Layout
18
Progress

• Integration
• Communication with kiosk software
• Phone management testing
• Update to report phone status
• Complete testing with kiosk

19
Future Goals

• Finish debugging and commenting assembly code
• Complete testing of phone functionality
• Fabricate new PCB to accommodate watchdog changes

20
Watchdog Redesign

• Old way
• AC relay directly on control box PCB
• Problems
• Crosstalk between AC and DC
• Dangerous

21
Watchdog Redesign

• New Way
• Physically cut power to the computer via AC relay
• Place AC relay on separate PCB from other
  operations
• Advantages
• Interface same for every computer
• Simple to install
• Solves DC/AC crosstalk problems
• Difficulties
• 120V AC (dangerous if not controlled)

22
Progress

• Watchdog Redesign
• Part Research
• Easy to find parts (Lafayette Electronic Supply)
• Schematic
• Prototyping
• Need to assemble and test a prototype

23
Future Goals

• Watchdog Redesign
• Complete and Debug Prototype
• Re-route and Fabricate Board
• Debug Fabricated Board

24
Scheduling Software
25
Scheduling Software Purpose

• Aid LCC staff with the scheduling of their 100
  volunteers
• Simplify the signup, assignment and display of
  shifts for volunteers

26
Previous Semester

• Purposely kept design simple
• Redesigned from the ground up using
• PHP
• MySQL
• XHTML standard
• CSS
• Currently able to make a scheduling run for LCC
  volunteers

27
What Needs to be Done Now

• Make volunteers availability form applicable for
  entire month
• Allow multiple users to sign-up for same slot
• Create separate schedules for R-SAP, On-Call, and
  Phone
• Create a flexible, dynamic sign-up for On-call
  and R-SAP volunteers

28
Current Progress

• Beginning to understand inner workings of
  previous scheduling software version
• Existing code running on each members respective
  server
• Found open source code for dynamic calendar
  (www.appideas.com)
• Merged calendars code into the scheduling
  software code

29
Demonstration
30
Our Plan

• Continue to learn how the current scheduling
  software works
• Determine additional variables needed
• Setup tables in database
• Send, store, and retrieve variables for each
  schedule (i.e. R-SAP)
• Show monthly/weekly view with dates and assigned
  volunteers names in appropriate time slots

31
Our Plan (cont.)

• Add color coding for days
• Increase functionality to allow multiple users to
  sign up for same slot
• Add check-box functionality for administration to
  assign shifts
• Add information showing number of slots requested
  and number of slots assigned

32
Roadblocks

• Limited programming experience
• Unfamiliar with PHP, HTML, and MySQL
• Poor documentation of existing code

33
Questions

• ?

34
THANK YOU !
35
(No Transcript)
36
New Design
37
(No Transcript)
38
(No Transcript)