1. Dec06-02: Parking Meter Ryan King: Team Leader Kristen Goering: Communications Justin Smith John Scapillato

2. Project Overview Project description Project description Description of End Product Description of End Product Intended Users and Uses Intended Users and Uses Assumptions and Limitations Assumptions and Limitations

3. Project Description Currently two Pay-for-Parking lots on campus Currently two Pay-for-Parking lots on campus Use computer based parking meters Use computer based parking meters Meters keep information about all stalls in the lot Meters keep information about all stalls in the lot Company who manufactures/maintains current system is out of business Company who manufactures/maintains current system is out of business DPS requested new meters be built DPS requested new meters be built

4. Project Description Currently have a unit built Currently have a unit built More functionality (talk about later) More functionality (talk about later) Greater access to maintenance Greater access to maintenance Fly in maintenance for old system Fly in maintenance for old system Testing phases have begun Testing phases have begun Trouble with the software license Trouble with the software license Hope to have unit outside before end of semester Hope to have unit outside before end of semester

5. Product Description Parking Lot: 1000 Spaces SM S

6. End Product Will be similar to existing meters Will be similar to existing meters Keypad and coin collector for input Keypad and coin collector for input LCD panel and printer for output LCD panel and printer for output

7. End Product Primary unit Primary unit Master and Slave Master and Slave Master has the database Master has the database Redundant Redundant Slave for input and output Slave for input and output Heater, thermal printer, drivers Heater, thermal printer, drivers

8. Intended Users and Uses Users Users First Class First Class Administrators Administrators Second Class Second Class DPS Employees DPS Employees Third Class Third Class Users of the parking lots Users of the parking lots Uses Add time to stalls Specific end-time Change entered Add money to multiple stations Lot statistics Remaining time Multiple Stalls

9. Assumptions The lot size will be equal or no more then 1000 spaces. The lot size will be equal or no more then 1000 spaces. Ac power will be provided to the unit. Ac power will be provided to the unit. The units will only accept nickels, dimes, and quarters as payment. The units will only accept nickels, dimes, and quarters as payment. The units will not provide change to customers The units will not provide change to customers Iowa State University Facilities Department will install the system Adequate finances will be available Parts list and assembly instructions provided

10. Limitations The system must allow for different rates, time of day, holidays rates. The system must allow for different rates, time of day, holidays rates. The units must allow users to add time to their current amount of time. The units must allow users to add time to their current amount of time. The hardware unit must provide the current payment status of the parking lot. The hardware unit must provide the current payment status of the parking lot. The servers unit must consist of two redundant processors with automatic failure protection. The servers unit must consist of two redundant processors with automatic failure protection. The user interface needs to be compact and easy to use. The hardware unit must print a receipt upon request. The server unit must have redundant storage The unit must be able to run for at least four hours if power goes out

11. Limitations DPS must be able to change rates and holidays without outside assistance. DPS must be able to change rates and holidays without outside assistance. The system must implement all the features of the current system. The system must implement all the features of the current system. The unit must withstand Iowa outdoor conditions. The unit must withstand Iowa outdoor conditions. The unit must be theft proof. The unit must be theft proof. Users should be able to add time to their current remaining amount Users should be able to add time to their current remaining amount The parts list for the subsequent units must consist of parts which are low-cost, interchangeable, backwards-compatible with the current prototype, and readily available Laptop system must be able to use USB connections for updating the unit. Laptop must be able to support the same software system as the unit.

12. Second Slave Unit Slave unit is a single processor unit Slave unit is a single processor unit The slave unit will retrieve information and act as the interface from which parking time is purchased The slave unit will retrieve information and act as the interface from which parking time is purchased The second slave unit will perform identically to the primary unit in hardware and software functionality, and user (customer/administrator/supervisor) interfaces The second slave unit will perform identically to the primary unit in hardware and software functionality, and user (customer/administrator/supervisor) interfaces Slave unit supports the user interface peripherals: coin acceptor, printer, keypad, and LCD screen Slave unit supports the user interface peripherals: coin acceptor, printer, keypad, and LCD screen Slave unit will have the software package that runs the interface between the user, the hardware, and the database Slave unit will have the software package that runs the interface between the user, the hardware, and the database

13. Slave Unit continued The development environment will be Windows XP Embedded Operating System The development environment will be Windows XP Embedded Operating System XP Embedded was chosen because it takes up less space and does not have the multimedia functionality that XP has XP Embedded was chosen because it takes up less space and does not have the multimedia functionality that XP has Exterior case will need to be developed for the second unit. This case will not need to be exactly like the case used for the primary unit Exterior case will need to be developed for the second unit. This case will not need to be exactly like the case used for the primary unit

14. Slave unit hardware block diagram

15. Testing Approach Software testing Software testing  Completed by previous phases Hardware testing Hardware testing  Individual components tested by previous phases, i.e. coin acceptor Field testing Field testing  Unit functions will be tested in lot per set of defined cases Simulation system testing Simulation system testing  Test with same defined cases as unit Software update system Software update system  Test unit functions after update by verifying with simulated results

16. Support Processes Considered Phone questions to support team Phone questions to support team E-mail questions to support team E-mail questions to support team Set up standard support system Set up standard support system  Create support e-mail account checked regularly in rotating shifts  Standard requests forms to be communicated through e-mail  On staff support team member to address problem and contact other support team members

17. Support Request Form

18. Support Solution Form

19. What About Software Updates? Currently, updated software would be difficult to upload to the system. Currently, updated software would be difficult to upload to the system. A monitor and keyboard would have to be taken to each unit. This is simply not practical. A monitor and keyboard would have to be taken to each unit. This is simply not practical. Ideally, the new software should be able to be uploaded quickly and easily. Ideally, the new software should be able to be uploaded quickly and easily.

20. Important Considerations A laptop can’t be connected to the unit and imitate an actual monitor and keyboard. A laptop can’t be connected to the unit and imitate an actual monitor and keyboard. Each unit is connected to a network. Each unit is connected to a network. A software updating system must be secure. A software updating system must be secure. The application does not need to be compiled on the machine it’s running on. The application does not need to be compiled on the machine it’s running on.

21. A Possible Solution A technician can take a laptop out to the unit and directly connect to the unit via the network. A technician can take a laptop out to the unit and directly connect to the unit via the network. Using remote desktop, the compiled application and it’s accompanying files can be put onto the unit to replace the old files. Using remote desktop, the compiled application and it’s accompanying files can be put onto the unit to replace the old files. Since this is a direct connection, there are no security issues. Since this is a direct connection, there are no security issues. Since the technician is at the unit, tests can be done to make sure the update was successful. Since the technician is at the unit, tests can be done to make sure the update was successful.

22. Questions?