Thursday, February 9, 2012

4. Proposed Design Solutions

So these screens were taken from my most recent progress presentation to my peers. It shows possible design solutions to answer my challenge/ question, and it was agreed that the first 2 solutions seemed to have the most promise, and would work effectively between all audiences. I definitely agree, and look forward to working with one of these directions. But the other solutions are certainly valid options and were well worth the time in the concept phase.









The first solution uses a combination of a smartphone application, and smaller, more simple GPS units called “beacons” handed out by DoT. So let me take you through the system. The app users start by turning on there application at the start of their rides. The beacon users simply turn their beacon on. After their ride is over, they turn them off. As the riders ride their route, satellites track and record their route to the smartphone application.  These routes can then be viewed individually or amassed as a single density map that can be sorted by time of day. DoT can then view this information to better place new bike safety measures.















The second solution uses the beacons, paired with roadside meters that are placed on every street. The riders turn on the beacons, at the beginning of their route, and turn them off at the end.  As they pass these roadside meters, which can be small and hidden from view, the meters count the cyclists, and display this on a simple  gauge. DoT can then view these meters and if the needles point to a set max number, DoT can know that road needs bike safety measures.














Solution 3 lets them take manuel control of the mapping process. The cyclist rides their route without any sort of device. Once at home or somewhere with computer access, the rider can input their route information to the application with other information like time of day they ride, and perhaps even problems they encountered on their route. The application then takes their route information and adds it to the mass of routes from other active users which DoT can then view.














Solution 4 uses driver operated GPS units to build information for the application. The driver simply turns on their GPS unit as they drive throughout the day. As they drive, if they encounter a cyclist around them all they have to do is tap the screen of their GPS, taking minimal attention away from their drive. The GPS unit takes that cyclist and sends it to the satellite, which adds them to a daily count of cyclists on that road and in the local area. Companies like Garmin or TomTom then send this information collectively to the application. and DoT can view it to make changes around the city.




This option uses a series of tickets or handout tokens that are placed in and collected at kiosks around the city. This system would have cyclists come in to DoT to register their bike. Tickets are handed out to these cyclists. When on their ride, the cyclist takes the tickets with them and places them in small collection beens at intersections or near street signs. DoT then collects these on a  routine basis, and uses them to count how many cyclists are using which roads. If the cyclist needs more tickets, they can pick them up from DoT. These tickets would be made of a durable material. So they could be given to new registering riders to use.

No comments:

Post a Comment