Wearable Computer Architecture and Applications Boeing Daniel P

© 2001 Carnegie Mellon University Aura Project 2

Five Generations of Wearable Computers Vu. Man 1 Vu. Man 2 Navigator 2 used for aircraft maintenance Navigator 1 Left, a look through the head mounted display. The user not only sees the aircraft maintenance interface, but also their work environment. Aura Project © 2001 Carnegie Mellon University Vu. Man 3 Navigator 2 3

© 2001 Carnegie Mellon University Aura Project 4

Wearable Applications and Architecture l l l Procedures - upload at completion Work Orders - incremental updates Collaboration - real time interaction » Client-Server – Thin Client Legacy Systems – Interactive Electronic Technical Manuals (IETMs) © 2001 Carnegie Mellon University Aura Project 5

Time Rate of Change of Data Taxonomy l l Procedures. Maintenance and plant operation applications are characterized by a large volume of information that varies slowly over time. A typical request consists of approximately ten pages of text and schematic drawings. Changes to the centralized information base can occur on a weekly basis. © 2001 Carnegie Mellon University Aura Project 6

Savings Using Tactical Information Assistants in Marine Heavy Vehicle Maintenance Current Practice SAVINGS FACTOR Vu. Man 3 Field Trials Personnel 2: 1 Current Practice SAVINGS FACTOR Vu. Man 3 Field Trials Inspection time 40% less © 2001 Carnegie Mellon University Aura Project 7

Four Month Design Cycle Initial visit 0 Story Boards Mock-up System 1 2 Prototype

Time Rate of Change of Data Taxonomy (continued) l l Work Orders. The trend is towards more customization in systems. Manufacturing or maintenance personnel receive a job list that describes the tasks and includes text and schematic documentation. This information can change on a daily or even hourly basis. © 2001 Carnegie Mellon University Aura Project 9

User Interface Screen © 2001 Carnegie Mellon University Aura Project 10

Time Rate of Change of Data Taxonomy (continued) l l Collaboration. An individual often requires assistance. In a “Help Desk” an experienced person is contacted for audio and visual assistance. The Help Desk can service many people simultaneously. Information can change on a minute-byminute and sometimes even a second-bysecond basis. © 2001 Carnegie Mellon University Aura Project 11

Integrated Technical Information for the Air Logistics Centers (ITI-ALC) Technology Demonstration © 2001 Carnegie

F-15 Depot maintenance © 2001 Carnegie Mellon University Aura Project 13

Problem l Outdated, cumbersome maintenance information capability » Paper-based products » Independent, uncoordinated computer

ITI-ALC Technology Demonstration Architecture Pentium Laptop Inspector Windows NT Server Oracle DB Inspection Wireless LAN Collaboration Engineer’s Workstation Mechanic © 2001 Carnegie Mellon University Aura Project 15

Evaluation & Inventory Current ITI-ALC 1. Login 1. Select aircraft 2. Select region 3. Pick-up 173’s 4. Check freq. defect list 5. Get tools 6. Conduct inspection 7. Check-off defect list 8. Stamp 173’s 9. Write up new defects 10. Access parts info. 11. Access TO’s 12. Access How. Mal codes 13. Write new defects in U-book 14. Stamp U-book 15. Enter data into database © 2001 Carnegie Mellon University 2. Hangar 4. Record Defects 3. 173 List 5. Add New Defect 4. 173 Signoff 5. 173 History Aura Project 6. Submit Defects 7. Defect History 16

© 2001 Carnegie Mellon University Aura Project 17

© 2001 Carnegie Mellon University Aura Project 18

© 2001 Carnegie Mellon University Aura Project 19

Engineering Assistance Current 1. Mechanic finds skin defect 2. Mechanic obtains Form 202 3. Fills in fields of Form 202 A 4. Views tech. data 5. Makes a rough sketch 6. Form to Scheduler 7. Form to Planner 8. Form to Engineering 9. Engineer reviews Form 202 A 10. Engineer researches problem 11. Engineer goes to hangar for visual 12. Engineer fills in Form 202 B 13. Reverse routing/logging above 14. Mechanic reads 202 B 15. Mechanic is ready to enact repair © 2001 Carnegie Mellon University ITI-ALC 1. ELogin 1. Login Screen 3 a. Parts Screen 2. Hangar Screen 3 b. Take Picture 3. Form 202 A 3 c. Sketch Tool 4. Confirmation Screen 3 d. Sound Tool 2. 202 B Aura Project. Selection Screen 3. Form 202 B 4. Confirmation Screen 20

© 2001 Carnegie Mellon University Aura Project 21

Wearable PC Runs Inmedius Web-based IETM Software Incremental Distribution Authoring IETM Authoring Web Runtime database schema incremental updates Server Web Browser incremental updates Web Server database schema IETM Engine incremental updates database schema IETM Authoring/Maint. Organizations F/A-18 Fleet Support Organization © 2001 Carnegie Mellon University Aura Project Client Fleet Operating Sites 22

IETM Display by Mobile Computer IBM Concept Model is an Example l Think. Pad 560 X Equivalent High Spec » Full Function Portable PC in IBM High Density Package l Ultimate Portability » Headphone Stereo Size System Unit, 2/3 lbs (299 g) l IBM Micro. Drive » 1" Disk, 5 mm Thickness, 20 g, 340 MB Capacity l Transparent Head Mount Display » Invented by IBM T. J. Watson Research © 2001 Carnegie Mellon University Aura Project 23

F-18 Inspection Application: Production vest fits under “Float Coat” © 2001 Carnegie Mellon University

11 Mbs wireless LAN connects Wearable Computer to server © 2001 Carnegie Mellon University

Selection of “hot links” with CMU’s Wheel/Pointer © 2001 Carnegie Mellon University Aura Project

Wireless and Handheld Andrew © 2001 Carnegie Mellon University Aura Project 27

Wireless Campus as of June 2000 300+ basestations Academic and Administrative Buildings Residence Halls,

Aura Thesis The most precious resource in computing is human attention Aura Goals • reduce user distraction • trade-off plentiful resources of Moore’s law for human attention • achieve this scalably for mobile users in a failure-prone, variable-resource environment © 2001 Carnegie Mellon University Aura Project 29

Context Aware Computing l l Applications that use context to provide taskrelevant information and/or services Context is any information that can be used to characterize the situation of an entity (person, place, or physical or computational object) Contextual sensing, adaptation, resource discovery, and augmentation Examples of Context Aware applications » Matchmaking » Proactive assistant © 2001 Carnegie Mellon University Aura Project 30

Example Agents Notification Agent l » Alert a user if they are passing within a certain distance of a task on their to do list. Meeting Reminder Agent l » Alerts a user if they are in danger of missing a meeting. Activity Recommendation Agent l » Recommends possible activities/meetings that a user might like to attend based on their interests. © 2001 Carnegie Mellon University Aura Project 31

Context Aware Computing Platform: The Spot Architecture © 2001 Carnegie Mellon University Aura Project

Spot Wearable Computer © 2001 Carnegie Mellon University Aura Project 33

Belt Worn Spot and Head Mounted Display © 2001 Carnegie Mellon University Aura Project

Research Challenges • User interface models—new application metaphors require experimentation • Input/output modalities—accuracy and ease of use • Quick Interface Evaluation Methodology—to use during design • Match capability with application—resist “highest performance” temptation © 2001 Carnegie Mellon University Aura Project 35