Public Works Engineering HATS: Handheld Asset Tracking System Final Interactive Prototype Presented...
-
Upload
audrey-nelson -
Category
Documents
-
view
218 -
download
0
Transcript of Public Works Engineering HATS: Handheld Asset Tracking System Final Interactive Prototype Presented...
Public Works Engineering HATS:
Handheld Asset Tracking SystemFinal Interactive Prototype
Presented by
Dave Nguyen and Margaret Yau
Background
Public Works Engineering (PWE)
Streets
Buildings
Residents
Coordinates Street Building Number of Residents
(3.434, 56.34, 78.89)
1000 Oxford Starbucks 0
(3.48, 78,38, 188, 34)
3999 Derby Lee’s Apartment
30
Geographical Information System(GIS)
Map
Overall Problem
Public Works Engineering (PWE) is currently digitizing locations and attributes of street assets in the city of Berkeley using a geographic information system (GIS). Our goal is to design a mobile, natural, and efficient interface that facilitates the process of field data collection.
Final UI Design: HATS
GPSReceiver
Global Positioning System
iPAQ
Customized ArcPad Application
(x, y, z)
Main
Map navigationUniversal icons
InformationGPS
On/off buttonDefault on
HelpExitData entry
Streetlight icon
Data Entry
If GPS is on, point averaging progress is shown on title bar
Fields for streetlight attributes
Help for this specific asset
Test Measures
Process DataFrustration/Confusion
Satisfaction
Bottom Line DataTime for learning
Time for completing the tasks
Number of errors
Process Results
Error TypesUsing manual map navigation tools while GPS is accessible
Identifying wattage was confusing
Didn’t use the GPS when it was available
Confused about using manual entry when GPS signal could not be acquired
Positive IncidentsLikes logging on. Allows tracking of recorder
Liked previous values being stored for next entry
Task Completion
0:000:140:280:430:571:121:261:401:55
Tim
e
1 2 3 Avg
Participant
Scenario Time per ParticipantScenario 1Scenario 2Scenario 3Avg
Hypothesis #1: The time needed for new users to complete each task will be less than 180 seconds (3 minutes)
Result: Each task took much less than 180 seconds, even for difficult scenarios (average 61 seconds)
Error Rates
Hypothesis #2: The number of errors for new users to complete the task will be less than 3
Result: On average, there was 1.7 errors across each scenario.
Out of 9 tests (3 users x 3 scenarios) there was 1 exception with 4 errors. 0
1
2345
6789
Err
or
Fre
qu
ency
1 2 3 Total
Participant
Error Frequency vs. Participants
Scenario 1
Scenario 2
Scenario 3
Avg
Learning Time
Hypothesis #3: The time needed to train will be less than 300 seconds (5 minutes)
Result: Each user, given less than 5 minutes of training, had, on average, 1.7 errors/scenario
3:363:433:503:574:044:124:194:264:33
Tim
e1 2 3 Avg
Participant
Training Time per Participant
Summary
PWE is digitizing locations and attributes of street assetsOur prototype is designed to improve the efficiency and accuracy of the data collection processHATS consists of an iPAQ running a customized ArcPad application and a GPS receiverThe bottom-line data of our user study satisfied our three hypotheses, while the process data led us to design changes that clarified the GPS status control