2. Agenda
• Overview
• Challenges
• What’s Ahead
• Summary

3. Wireless for the Enterprise
• Backend Application Access
– Email
– PIM (Personal Information Management)
– CRM/ERP
• Custom/Vertical Applications
– Customer Service
– Financial Management
– Health Care
– Extended ERP Functionality
• Data Access
– Right time
– Right user
– Right format
• Etc.

4. Today’s Technology Issues
• Lack of Interoperability Among Devices
• Competing Incompatible Wireless Network
Standards
• Coverage Issues
• Heightened Security Concerns
• Complicated Application Development

5. Challenges
• Management
• Devices
• Networks
• Platform

6. Management
 Problems
 Administration
 User Management
 Device Management
 Application Management
 Versioning Control
 Managed Services
 Multi-carrier agreements
 Carrier Inter-operability
 Multiple protocols
 Multiple Bills/User
Tracking
 Logistics
 Maintenance
 Problems
 Platform
 Device dependent
functionality
 Security
 Multiple Device-neutral
delivery platform

7. Challenges - Networks

8. Today’s Networks
• GSM – Europe’s current wireless standard
• iMode – DoCoMo technology
• CDPD – AT&T data service
• Mobitex & DataTac
• Other networks
– Metricom
• Wireless LANs
– 802.11b

9. Tomorrow’s Networks
• 2.5G
– GPRS
– 1XRTT
– EDGE
• 3G (3rd
generation) high speed, packet switched
– UMTS
– HDR
– EDGE
• Wireless LANs
– 802.11a
– Bluetooth

10. Challenges - Devices

11. Devices – RIM 950/850, 957/857
• “Always on” wireless data device
• Low power 386 chip
• Storage up to 5 MB
• Works over Mobitex, DataTac, GPRS
• Runs BlackBerry Email service

12. Devices – Pocket PC
• Lots of different chips
– Up to 206 MHz
• Storage up to 64 MB
• Wireless requires a full-size card (e.g., Sierra
Wireless)
• Most robust platform for development

13. Devices - Palm
• Defined the market
• Lots of software
• Motorola Dragonball chip up to 20 MHz
• Wireless through Omnisky
• Memory up to 8 MB (or memory stick)

14. Devices - Other
• PC variants (palmtops, laptops)
• Smartphones
• Pagers
• Tablet

15. Challenges - Platform

16. Current Approach
Extend the web paradigm via transcoding techniques.
On-line Paradigm Assumes
• Existing content can simply be
“Ported”
• A fat pipe exists
• Network is always there
• All desk top information is
appropriate on a small device
• People are patient

17. Current Market Approach Fails
• Only need to present
relevant data
• 19.2kbs is prevalent
• Must find ways to “speed” up
development and delivery
• Networks Unreliable
• Mobile Applications
• Broadband networks are in
the distant future
• Must use a framework
• Off-line capabilities and synching
The Reality Vaultus Solution

18. Development and Delivery Architecture

19. A migration path
 An architecture for today and tomorrow
 While geared to J2ME devices, it
 Recognizes investment made in existing technologies and devices
 Uses email as the least common denominator
 Benefits
 Common architecture for the long run
 Enables an evolutionary approach that acknowledges that change is
constant….Business Processes, Technology, Devices
J2ME
Non – J2ME
Parsing
Engine
Platform
Evolution
1 2 3

20. Mobile solutions represent technology
complexity
Delivery Platform
• Multiple back ends
• Security
• Technology hosting
• Version control
Data Transport
• Security
• Multiple networks
• Optimization
• Network coverage
• Bandwidth
End User
• Access control
• Multiple devices
• Content customization
• Personalization
Solution Management
• Provisioning
• Billing
• Support
Mobile Solution Characteristics

21. Promise of Mobile Applications
Potential Mobile Data Adoption and ROI by Vertical Industry Sector

22. Resources
• www.anywhereyougo.com
• www.portablelife.com
• www.wirelessdevnet.com
• www.handhelds.org
• www.rim.net
• www.pocketpc.com
• www.palmos.com/dev