case study: mobile performance support for maintenance procedures
DESCRIPTION
My presentation for Learning Solutions 2011.TRANSCRIPT
Session 607 - Case Study:
Mobile Performance Support for Maintenance Procedures
Christopher AdamsHandshaw, Inc.
3.24.2011
Project Description
• Enable maintenance technicians to access and complete Maintenance Procedure Cards (MPCs) on a hand-held device.
87’ Coastal Patrol Boat (WPB)
2
3
Project Participants
4
Project Phases
PrototypeDevice
SelectionContent Capture
App Development
Pilot
5
Prototype
• Created content structure and one page of content (text and video) in an existing learning content management solution.
• Accessed content through wirelessly connected mobile phone.
• Used simple demo to gather requirements.
PrototypeDevice
SelectionContent Capture
App Development
Pilot
6
Lessons Learned
• Our mobile solution was not as mobile as we thought it would be.
PrototypeDevice
SelectionContent Capture
App Development
Pilot
7
Device Selection
• Used original prototype plus a laptop and router to play the role of the internet.
• Had actual maintenance technicians in repair docks handle a number of potential devices.
• Informal evaluation included responses to menu navigation, readability, text entry, and form-factor.
PrototypeDevice
SelectionContent Capture
App Development
Pilot
8
PrototypeDevice
SelectionContent Capture
App Development
Pilot
9
PrototypeDevice
SelectionContent Capture
App Development
Pilot
T h i s s l i d e
l e f t
i n t e n t i o n a l l
y b l a n k s o
t h a t C h r i s
d o e s n ’t g e t
t w i t c h y a n d
r u i n t h e
s u r p r i s e !
Guess Which Two Devices Won?
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Trimble Yuma HP Mini 100e
Rugged outdoor tablet computer.
Durable netbookdesigned for education.
11
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Trimble Yuma HP Mini 100e
Rugged outdoor tablet computer.
Durable netbookdesigned for education.
12
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Lessons Learned
• Our hand-held solution will require large hands.
• Both of our mobile platforms turned out to be full-on Windows 7 devices.
13
PrototypeDevice
SelectionContent Capture
App Development
Pilot
The Late Addition
Viewsonic G Android Tablet
14
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Content Capture
• Content existed in Word documents, PDF documents, and paper MPCs.
• Team of writers worked to “chunk” and import data using LCMS front-end.
• Produced 567 procedures for pilot in roughly two months (estimated at about 1/6 of total procedures).
• Custom “cleaner” built to correct and standardize formatting from original documents.
• Images and video were captured and edited for a subset of produced procedures.
15
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Content Structure
Asset
Sub-System
Procedure
Item Grouping
Item
16
PrototypeDevice
SelectionContent Capture
App Development
Pilot
LCMS Interface
17
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Why a Content Management System?
Definition:
A content management system (CMS) is the collection of procedures used to manage work flow in a collaborative environment. These procedures can be manual or computer-based.
- adapted from Wikipedia
18
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Why a Content Management System?
Attributes:
• Allow for a large number of people to contribute to and share stored data
• Control access to data, based on user roles. User roles define what information each user can view or edit
• Aid in easy storage and retrieval of data
• Reduce repetitive duplicate input
• Improve communication between users
19
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Content Standardization and Integration
Asset VendorSpecifications
Content Components
Text
Media
Deliverables
Performance Support
Training
Documentation
20
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Why a Content Management System?
Attributes:
• Organizes content by objective
• Presents content as activities
• Integrates with Learning Management Systems
l e a r n i n g
21
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Solution Architecture
• LCMS• XML Stager
Desktop Synch App
Android Mobile App
WindowsMobile App
Periodic Secure Internet
Connection
Once-per-shift Wired
Connection
22
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Desktop App - Synch with Stager
23
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Desktop App - Synch with Device
24
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Windows Mobile App – Sign In
25
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Windows Mobile App – Procedure Selection
26
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Windows Mobile App – Content Example
27
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Windows Mobile App – Content Example
28
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Windows Mobile App – Data Capture
29
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Android App Differences
30
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Desktop App – User Actions
31
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Lessons Learned
• Mobile video formats needed a lot of tweaking.
• Parsing XML on a mobile device is much slower than expected.
• Native media apps are best.
• Having a SCORM framework on a disconnected device is handy.
32
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Pilot
• Running on three assets since fall of last year.
• Well received so far by technicians.
• Proposal to extend pilot pending.
33
PrototypeDevice
SelectionContent Capture
App Development
Pilot
Potential Future Directions
• Additional apps for additional platforms.
• Integration to inventory and work management systems.
• Integration with LMS(s).
• S1000D import/export.
34
Thank You!
For more info:
www.handshaw.com
blog.learnbombs.com
Christopher AdamsHandshaw, Inc.
3.24.2011
36
If You Must Know – Rough Scope of Work
Prototype
• 1 Resources
• 2 Days
Device Selection
• 4 Resources
• 1 Month
Content Capture
• 6 Resources
• 2 Months
App Development
• 2 Resources
• 2 Months
Pilot
• 1 Resource
• 1 Month
37
38
39
40