1. Team 1: Staff Dan Piessens Henrik Gustavsson David Luu Brent Wellner
BSEE / BSCS
BSEE

2. Team 1: Expertise & Experience
Dan Piessens
Henrik Gustavsson
David Luu
Brent Wellner
Expertise: PLD/FPGA, Microprocessors, Software
Experience: 5 yrs software development
Expertise: Microprocessors, AutoCAD, Software
Experience: 6 semesters TetraPak
Expertise: AC/DC Conversion, MathCAD, Matlab
Experience: N/A
Expertise: PLD/FPGA, VHDL
Experience: 1.5 yrs Modine Manufacturing

3. Team 1: Contact Info
Dan Piessens
Henrik Gustavsson
David Luu
Brent Wellner
Phone: (414)
Phone: (262)
Phone: (414)
Phone: (920)

4. Team 1: Weekly Availability Worksheet
Dan Piessens
Henrik Gusatvsson
David Luu
Brent Wellner
Time 1: M/W 12:30 - …. Time 2: F/S/Su
Time 3: T 1:00 - 3:30 Time 4:
Time 1: M/W 12:30 - 3:30 Time 2: T/Th - 3:30
Time 3: M/W 6:30 - …. Time 4: F/S/Su
Time 1: M/W 1:00 - 3:00 Time 2: F/S/Su
Time 3: T …. - 6:30 Time 4:
Time 1: M/W …. - 5:00 Time 2: Su
Time 3: T/Th …. - 6:30 Time 4:

5. Team 1: Weekly Project Meeting Plan
Weekly Meeting 1: IEEE Office, Thursday 01/27/05 8: :30 PM
Dan, All attendees & Purpose: Discuss Project Objectives
Weekly Meeting 2: IEEE Office, Tuesday 02/01/05 1:00 - 3:00 PM
Henrik, All attendees & Purpose: Expand on Project Ideas
Weekly Meeting 3: IEEE Office, Tuesday 02/08/05 1:00 - 3:00 PM
David, All attendees & Purpose: Finalize Project Selection
Weekly Meeting 4: IEEE Office, Tuesday 02/15/05 1:00 - 3:00 PM
Brent, All attendees & Purpose:
Weekly Meeting 5: IEEE Office, Tuesday 02/22/05 1:00 - 3:00 PM
TBA, All attendees & Purpose:
Weekly Meeting 6: IEEE Office, Tuesday 03/01/05 1:00 - 3:00 PM
Weekly Meeting 6: IEEE Office, Tuesday 03/08/05 1:00 - 3:00 PM
Weekly Meeting 6: IEEE Office, Tuesday 03/15/05 1:00 - 3:00 PM
Weekly Meeting 6: IEEE Office, Tuesday 03/22/05 1:00 - 3:00 PM
Weekly Meeting 6: IEEE Office, Tuesday 03/29/05 1:00 - 3:00 PM
Note: Meeting Owners Send Weekly Notices, Record Business-Issues-Actions, Keep Weekly Attendance Records

6. Team 1: Total Resources
1000 Man-hours (Including: lab, weekly meetings, individual commitments )
$400 or key part availability for material and prototyping

7. Team 1: Decision Making
Decisions will be made through a consensus, based upon: resources, time consumption and cost.
Majority vote applies in the event of an irresolvable conflict.

8. Roles to Define & Assign
Project Integrator: Dan Piessens - Owns weekly progress reports to TA. Logistics and communication of team meetings. Develops and Tracks overall project plan. Integrates Block design plans. Tracks expenditures. Owns project level verification and validation plan, capture and documentation of results.
Presentation Mgr: Henrik Gustavsson - Owns master MS Powerpoint slide set for team including formats, logos, fonts, colors, header/footer, backgrounds, rev control, submission of master floppy or CD for P1-P4 and Final Presentation.
Report Mgr: Brent Wellner - Owns master MS Word document for team including revision control, formats, logos, fonts, colors, header/footer, table of contents, submission of master floppy or CD for Final report.
Archive Web Mgr: Dan Piessens - Owns weekly backup of all electronic material generated that week. Backup for Presentation Mgr and Report Mgr. Management of any team Web site resources.
Assembly & Proto Mgr: Brent Wellner - Owns overall assembly level definitions, basic assembly drawings, master prototype & product parts lists, collection of block parts lists, procurement of proto components. Overall prototype mechanical and electrical assembly
PCB Layout Mgr: David Luu - Owns overall PCB layout, Block to PCB mapping, PCB tools, PCB design drawings, PCB procurement, PCB assembly including special tools, soldering, wire-wrapping, drilling, and gluing.

9. Catch-a-Buzz Buzzer system Why is this a good project?
This system is designed for users to participate in games like a quiz bowl. Users would be able to hit a button on a remote unit that would transmit the response wirelessly to a center console that indicates who responded and keeps track of a scores. Alternately user can respond to a multiple choice question, the console would then indicate the correct answer and score.
Buzzer system
Allows for 1 to N remote units
Master console that indicates responses and team scores
Two operation modes:
First unit to respond
Correct answer multiple choice
Display team scores either on LCD or TV out
Why is this a good project?
Large target market: schools, organizations, weddings
Easy to use for people, simple remote interface
Utilizes the skill of each team member fully

10. Catch-a-Buzz - Block Diagram
Console Unit
Remote Unit
Power
120V Transformer
RF Transceiver
Power
Battery
RF Transceiver
Microprocessor
CPLD
LCD Display / LED
Keypad Input
LED / 7 Segment Display
Button Input

11. RF controlled Belaying Machine
The RF controlled belaying machine is a device intended for use by rock climbers in an indoor rock climbing facility. The primary objective of this device is to substitute the use of a human belayer through the safe use of a belaying machine.
The key performance aspect of this device is that it eliminates the use of a belayer when indoor rock climbing. It delivers all control to the climber through a simple RF module which controls the various modes in which the machine can be used.
The base/motor drive is powered by a typical 120V power outlet. The remote unit is Li-polymer powered and is recharged through a unit positioned on the base/motor drive. The user interface consists of a pushbutton type user interface with confirmation LED’s for each command. The user interface controls the different modes of operation: belay, slack adjustment, stop and rappel.
This project is a good fit for the team due to it’s interesting and practical nature. An RF controlled belaying machine does not exist, it would be the first of it’s kind. It’s marketability is very plausible for all indoor rock climbing centers.

12. Belaying Machine - Block Diagram
Base / Motor Drive
Remote Transceiver
Remote Charger
Transceiver
Transceiver
Input / LED’s
CPU
CPLD
Power Supply
Motor / Drive
Power Supply

13. Enroute - Overview Transit Notification System
This system consists of units at each bus stop that communicate with a remote on every running bus. This allows a bus to only stop at a bus stop if notified by the unit at the station. The users notify the bus via push buttons on the station transceiver. Both Transceivers are programmable via a keypad on their respective units. The station transceiver also contains a taxi call but that sends a request to a server via a network interface.

14. Enroute - Features Station Transceiver Unit Bus Transceiver Unit
Ability to request different busses via push buttons
Programmable via keypad
network interface for taxi notification and confirmation
Powered by 120V transformer
Bus pickup notification
Bus Transceiver Unit
LCD display for stop notification
Communicates with stations via RF transceivers
Powered by 12V DC to DC transformer
Post-pickup cancellation

15. Enroute - Block Diagram
Bus Transceiver Unit
Station Transceiver Unit
U.I. 1
Transceiver
Transceiver
NIC
Henrik
U.I. 2
CPU1
CPU2
Dan
Brent
PSU 1
Setup Controls
PSU 2
Setup Controls
David

16. Enroute - Justification
Why is this a good project?
Large target market: useful in any city with a public transit system.
No competitive products exist: Unique to the transportation market
Easy to use for people, simple interfaces on both ends
Reduces ride time and thus money
Convenience of notifying taxies
Fully utilizes the skill of each team member

17. Enroute - Product Selection Process
Major Risks
Too many blocks - overly complicate design
Why were other projects rejected?
Other projects were not as closely related to our individual expertise
Mechanical challenges with the Belaying machine
Lack of marketability for the Catch-A-Buzz product
Product Selection
Project selection was unanimous

18. Standard System Level Requirements
Standard Requirements
Environment:
Operating Temperature Range: -40 to 70 °C
Operating Humidity Range: 2 to 98 %
Storage Temperature Range: -30 to 80 °C
Storage Humidity Range: 2 to 98 %
Storage Duration: 2 Years
Energy Sources:
120V AC ( V), 12V DC (10-15V)
Over Voltage Protection Circuitry

19. Standard System Level Requirements
Standard Requirements
Mechanical:
T.b.d.
Life Cycle:
Production Life 5 Years
Full Warranty Period: 1 Year
Service Strategy: Distributor Repair

20. Performance System Level Requirements
Performance Requirements
Power Inputs:
AC power input ranging from Hz (Station Unit)
12V DC input (Bus Unit)
Over Voltage Protection
Electrical Functions:
T.b.d.
Electrical Interfaces:
Analog, Digital and Power Signals
Bi-Directional RF Transceivers
RS232 Network Interface

21. Performance System Level Requirements
Performance Requirements
Operator I/F Outputs:
LED
Momentary Pushbutton
16 Digit Matrix Numeric Keypad
16 x 2 LCD Display
Power Modes of Operation:
ON/AC
Calibration Modes:
Program Mode
Configure Mode

22. Performance System Level Requirements
Performance Requirements
Mechanical Interfaces:
Mounting Brackets
Optic Sensor (for backlight of LCD)
RS232 Connectors
Safety
Power Signal Current Limit Max = 1.2 Amps
Ground Fault Protection

23. Basic Business Case
Estimate the Average Product Selling Price (ASP$): $200 (Base) / $100 (Bus)
Estimate the Product Annual Sales Volume: 2,000,000 (Base) / 1,000,000 (Bus)
Estimate the Per Unit Cost of all Parts and Materials using the above annual volume assumption: $130 (Base) / $50 (Bus)
Estimate the Per Unit Cost of all the Assembly, Test and Mfg using the above annual volume assumption: $20 (Base) / $20 (Bus)
Estimate the Total Development Cost in $ incl. Labor & Material: $500,000
Calculate the Annual Sales $ = 500 M
Calculate the Per Unit CM$ = $150 (Base) / $70 (Bus)
Calculate the CM% = (Base) / 0.70 (Bus)
Calculate the Annual CM$ = $362.5 M
Calculate the ROI Time in Years = 0.01 Years