Agenda

• Overview• Challenges• What’s Ahead• Summary

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.

Today’s Technology Issues

• Lack of Interoperability Among Devices• Competing Incompatible Wireless Network

Standards• Coverage Issues• Heightened Security Concerns• Complicated Application Development

Challenges

• Management• Devices• Networks• Platform

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

Challenges - Networks

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

Tomorrow’s Networks

• 2.5G – GPRS– 1XRTT– EDGE

• 3G (3rd generation) high speed, packet switched– UMTS– HDR– EDGE

• Wireless LANs– 802.11a– Bluetooth

Challenges - Devices

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

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

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)

Devices - Other

• PC variants (palmtops, laptops)• Smartphones• Pagers• Tablet

Challenges - Platform

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

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

Development and Delivery Architecture

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 – J2MEParsing Engine

Platform

Evolution

1 2 3

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

Promise of Mobile ApplicationsPotential Mobile Data Adoption and ROI by Vertical Industry Sector

Resources

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