Kevin Benedict Ponders the Future: palm

Showing posts with label palm. Show all posts

HP Buys Palm - RIP

Interesting news I hadn't considered - HP as a suitor for Palm.

"Palm's innovative operating system provides an ideal platform to expand HP's mobility strategy and create a unique HP experience spanning multiple mobile connected devices," Todd Bradley, vice president of HP, said in a prepared statement.

It is fascinating to me when a brand goes bad. Sometimes I think the morale in a company goes bad years before and it rots from the inside out. Employees warn their peers to stay away, recruiting suffers and vacations become the topic of choice. People stay at the company drawing a paycheck long after they give up on its success. They go through the motions but have no belief. Social networking enables industry pundits to sense the demise even before the market does.

I have known many companies in my time where if the staff were given an anonymous survey, they would have predicted its demise years earlier than the fact.

***************************************************
Kevin Benedict
Author of the report Enterprise Mobile Data Solutions, 2009
Mobile Strategy Consultant, Mobile Industry Analyst and Web 2.0 Marketing Expert
http://www.netcentric-strategies.com/
www.linkedin.com/in/kevinbenedict
twitter: http://twitter.com/krbenedict
http://kevinbenedict.ulitzer.com/
http://mobileenterprisestrategies.blogspot.com/
***Full Disclosure: I am an independent mobility consultant and Web 2.0 marketing expert. I work with and have worked with many of the companies mentioned in my articles. ***************************************************

SAP’s Mobility Challenge, Part 1

I am very interested in watching SAP's emerging mobility strategy as it matures, evolves and morphs yet again. I am not critical; this is how all of mobility is these days. Four years ago we were all using the term Palm, Pocket PC and PDA. Now we are speaking of iPhone, Android, RIM and iPads. Within these different technologies are literally hundreds of different mobile applications and mobile extensions that can add value to SAP's ecosystem. I have been seeing a lot of activity in this space. I have seen SAP partnership announcements with RIM (Blackberry folks), Sybase, Sky Technologies, Syclo and ClickSoftware. I have seen SAP comments from many different industry and solution groups within SAP related to mobility.

What I believe is particularly challenging to SAP is trying to determine if mobility is an extension of an industry business process, or an integrated technology platform. Let me provide three examples of the challenge – work order management is both a back office solution and a mobile client (work orders are dispatched to mobile handheld computers in the field that are carried by the service technicians). Likewise, asset management involves both back office solutions and a mobile client (inspectors, facilities managers, plant maintenance teams and service technicians use mobile clients). Route/Sales management also involves back office solutions and mobile clients (route sales people track sales, inventory, delivery and promotions on mobile devices). So are the mobile applications/clients part of the work order management, asset management or route management categories or do they justify an integrated SAP mobility platform? What do you think?

I image this is a very complex and difficult discussion within SAP. SAP has selected specific partnerships within different industry verticals. These partners are often producing their own mobile applications to extend the capabilities of their solutions; however, these mobile solutions may in fact not align with SAP's overall mobile platform strategy.

From a purely technology perspective, it may make more sense for SAP to develop or select a MEAP (mobile enterprise application platform) that best integrates and supports SAP's underlying architecture and product roadmap, however, their vertical industry partners would not like this strategy at all as they see mobility as a major growth area for them. Very interesting times indeed!

Read SAP's Mobility Challenge, Part 2 here.

Mobile Applications and 69 Enterprise Support Questions

Often the focus of a mobile software project is on gathering the functional requirements, designing, developing and deploying the mobile solution, but little or no advanced planning is given to the question of how to support it once it is deployed. The following list contains many of the questions your IT helpdesk and support department will want and need to know:

Who does the field worker call if there is a mobile device problem?
Who does the field worker call if their mobile application is not synchronizing correctly?
Who trains new employees on how to use the mobile device and application?
If there is a mobile software problem, who fixes it - IT, consultant, contractor, your systems integrator or VAR? How do you get in contact with them?
Who does the field worker call if the mobile application needs edited or upgraded?
If the user downloads a new version of the mobile operating system and the mobile application doesn't work, who will fix it?
How do you prevent mobile users from downloading new software applications that might break the system?
How do you back-up mobile devices so the information is centralized?
Who owns and defines the business process you have mobilized? They may need to approve any changes to the business process.
Who controls the security of the device?
How do you set-up a new user to securely access the enterprise database?
What kinds of security rules must the field user follow?
Do different users have different security profiles?
Is there a standard set of security rules for mobile devices across the enterprise?
Who controls access to the enterprise database application (a DBA)?
Will the Database Administrator allow you to synchronize data directly to their enterprise database application, or do they want a "staging database" or API layer to review all data before it is loaded to the enteprise database application. They will likely be involved in any future changes to the mobile application.
Are synchronizations done in real-time, near-real-time, or batch on a schedule?
Does one mobile device have multiple synchronizing applications? Are they on different schedules or do they synchronize at the same time?
How many different enterprise database applications are synchronizing with a mobile device? If there is a sync problem, how do you know what database applications may be impacted?
If you hire an additional field worker, how do you order an additional mobile device? Whose budget covers this? Who is the vendor? What support plan or insurance plan should be included?
Who decides if the new mobile device needs to be ruggedized or a consumer grade? What level of ruggedness is required for the specific user?
Do different job functions require different devices, carriers and wireless data service plans?
Who decides what brand of mobile devices are going to be the company standard?
Where do you purchase your mobile devices if one breaks or you need to add one to your inventory? Do you have a corporate discount or volume discount agreement?
How do you manage and control the variable costs of using a data plan from a local wireless carrier? What happens if the costs of the data services gets out of control? Who pays for it?
Are the mobile devices or the mobile software solutions under warranty? Where are these contracts stored? Who owns them?
Is there a yearly support contract IT needs to know about? How much? Whose budget?
What is the account number the warranty is under?
How do you set-up a new data plan for a new user with your wireless carrier? Who does that in the company? What is the account number so you can add subscribers? Whose budget pays for it?
What happens when Microsoft releases a new Windows Mobile operating system and you can only purchase mobile devices with the new OS on them? Who is going to upgrade your mobile software solutions so they work with the new OS?
What happens when the field engineer treks across 2 miles of muddy field to work at a construction site, but the battery on his handheld computer dies about 10 minutes after he gets there? What is the backup battery plan?
What happens when text messages, photos, videos, music, and games claim all the memory on the rugged PDA and the Construction application becomes either too slow or unreliable because of low memory?
How do you know when your mobile workers are synchronizing the latest information? You don't want mobile workers going days without synchronizing their device.
When you send an updated software application to your mobile workers, how do you know who is using the new application and who is still on the old?
How do you disable synchronization on a lost or stolen mobile device?
How do you kill and/or protect your data on the mobile device if it is lost or stolen?
How do you keep track of which workers are using which mobile devices? If there is an operating system update, or firmware update, how do you know who needs it?
What is the process for bringing mobile handhelds into the IT department for repairs and upgrades? Is there a central location, or should various locations be scheduled on specific dates.
If you are taking care of many different mobile field workers and many different mobile devices with a variety of operating systems, wireless carriers and screen sizes, how do you track who gets what?
If you have a project manager that requires visibility to more data than other workers, how do you manage different views on the handheld computer?
Some mobile projects require different levels of security, for different levels of data visibility. How would you manage and track that?
Will your company standardize on 1 mobile operating systems or several (Blackberry, Microsoft Windows Mobile, Palm, Android, iPhone, etc)
Some applications require barcode, RFID, GPS, digital camera and other specialized data collection accessories, while others don't. How does the IT Helpdesk track the brand, version and other details of these accessories?
If a dump truck backs over your supervisor's $1800 ruggedized computer and crushes it into hundreds of unidentifiable pieces, how do you get a replacement out to the supervisor with the exact application and data that is required as quickly as possible?
If a mobile device needs repaired - what is the process for keeping your field workers operating without it? Do you have a stock of spare mobile devices?
Does your mobile device reseller have a replacement program?
How do you deploy new mobile applications to your 1,300 mobile device users? Must they bring all their devices back to the IT department, or can you publish new applications directly to the handheld computer?
How do you support the mobile device, when the user has limited computer knowledge and is sitting on the top of a utility pole? What tools can the IT Helpdesk use to remotely help and diagnose problems?
How do you recognize a defective mobile device that is being shared by 12 different mobile workers? Do you have a method of identifying which problems are being reported on a particular device or are you logging support calls only by users?
What is your process for dispatching work orders to service technicians when they are disconnected or out of range of cellular and wireless networks? A process needs to be defined.
What is your synchronization plan for each mobile worker? Can they sync in the morning and evening at their office desk, or do they need to sync every 5 minutes or in real-time?
What is the synchronization plan for a service technician that rarely has wireless network access? Does it justify a satellite up-link? (Sears Service Technicians use both)
How do you know when information was successfully synchronized with a mobile device in the field? Can you see and determine the success of the synchronization from the IT Helpdesk?
What is an acceptable synchronization time? Is it 20 seconds, 2 minutes, 20 minutes? Does the IT Helpdesk know what times are acceptable so they can consider this when configuring a new user?
Does all data need to be synchronized in real-time, or only some. Product catalogs are an example of updates that may only be needed weekly or monthly?
How much data can be synchronized in a given period of time on the chosen connectivity option? Is that an acceptable speed for the task at hand?
Who determines the hardware requirements that support the mobile application and desired synchronization speeds?
When a new mobile software application is developed, who tests its operating speed on different devices, processors, memory levels and connectivity options to determine what is acceptable and what is not?
When you are updating or reconfiguring an enterprise database, how do you know what mobile applications and mobile users will be impacted by these changes? How do you manage this update process?
How does the IT Helpdesk know which one of the 17 mobile applications on the handheld computer is having a synchronization problem?
If you are supporting 174 work crews and their mobile devices around the globe, how do you know where they are located, and who is responsible for them?
How does the IT Helpdesk know if a mobile device is using a cradle, modem, bluetooth, wireless, USB, satellite or Cellular connection to synchronize? The IT Helpdesk really wants to know before they begin working on the issue.
What wireless carrier, technology and through-put speed is the mobile device using? Is it GPRS, GSM, CDMA, Edge or some other network configuration?
Do you need to stagger the synchronization times? One of my clients had a problem with 300 mobile workers downloading large product catalogs all at the same time each month -the first Monday of the month. This caused a bottleneck and slow downloading times.
What do you do with old and retired mobile handheld devices? Companies like Ryzex buy back old handheld mobile devices and recycle them.
What rugged or semi-rugged cases are required to protect the mobile device?
What add on assessories are supported on the mobile device? Ear pieces, GPS, add-on RFID, barcode scanners? Who supports these and where do you order replacements?
Does the same mobile software application work on rugged mobile handhelds and on mobile consumer devices?
What employees and roles get the different levels of rugged devices?
Do you have a corporate account with a mobile device reseller that will repair all of the different mobile devices or do you work with many different vendors with different support and warranty plans.

All of these questions are very important and need to be answered upfront. If you would like to discuss this subject in more detail please email me.

***********************************************
http://mobileenterprisestrategies.blogspot.com
***********************************************

Microsoft's Mobile Software Industry Growth Projections

Microsoft and Palm talk about the latest trends in the mobile software, smartphone and handheld PDA industry in this webinar.

Microsoft, Palm and MobileDataforce Team Up for Handheld PDA and Smartphone Campaign

Microsoft, Palm and MobileDataforce team up to provide small to medium sized companies with cost effective mobile field services applications for use on smartphones and handheld PDAs. Here is the slogan:

Mobile Field Service Workers. Wireless access. Get it Done.

Deliver mobile work orders, inspections, up-to-date asset information, and more with the PointSync Mobility Platform & Palm® Treo™ smartphones

How valuable would it be for your field services team to easily access mobile work orders, wireless pick lists, inspections and up-to-date asset information on their Palm® Treo™ smartphones?

Join Palm and MobileDataforce for a live, interactive Webinar to find out how. By attending, learn how to qualify for a free 30-day trial of the MobileDataforce PointSync® Mobility Platform and a Palm Treo 750 smartphone.

Qualified users for the trial will also receive a free mobile consultation and discounted pricing from MobileDataforce – and up to four hours of mobile solution consulting for free! And... Get all your mobile field service questions answered live during the Webinar by representatives from Palm, Microsoft and MobileDataforce.

Discover how MobileDataforce PointSync on Palm Treo smartphones can help your company:

Deliver work orders, inspection forms, asset management and more to your field service workers

Sync two-way data from the point of business to help save time, improve accuracy, and avoid misplaced forms

Consolidate multiple mobile devices into a single Windows Mobile® smartphone that delivers voice, email, text messaging, and mobile field service applications2

Create your own mobile applications, or have the MobileDataforce Professional Services team complete and deploy a solution for you

Stay ahead of the competition and help ensure top-level customer service

We look forward to seeing you at the Webinar. Join us to take advantage of the opportunity to get a free, no obligation trial offer and realize the mobility benefits of this solution for your field services team.2

Warnings for Companies Considering Mobile Handheld PDA Business Solutions

MobileDataforce is very busy these days helping companies replace old mobile software solutions for handheld PDAs that were based on out-dated Palm or Pocket PC operating systems. Although we appreciate the business, it is worth highlighting this issue for companies considering whether to program/code their own mobile software solution, or use a supported mobile middleware platform like the PointSync Mobility Platform.

Here are some issues to consider:

Is your mobile solution going to be upgraded every year as mobile operating systems and handheld computers are upgraded?

Who is going to be your in-house expert on the latest mobile operating systems and how to support them? It will take an investment of resources to stay current.

When you buy new handheld computers or PDAs, they are generally sold with only the latest most current operating system on them. So how can you buy new handheld computers, unless your mobile solution can run on the latest operating system. Over the life of your mobile software application you may need to upgrade the OS many times.

Often a business unit funded the original mobile software application development project. Are they willing to continue funding your mobile operating system upgrades each year. The answer is most often NO! So how can IT support it after the first year?

One solution to prolonging the life of a mobile software application is to pre-purchase all the handheld computers or PDAs you will ever need. This will ensure that you have the supported hardware and supported operating system available to you over the life of your mobile software application. But let's be real....who is going to fund a pre-purchase of all the hardware you will ever need? No business unit I have ever met. If you find one, let me know...I would like to sell them all the mobile software they will ever need in the future as well.

The most reasonable approach to keeping current with mobile operating systems and the latest handheld computers and PDAs is to develop your mobile handheld application on a supported mobile software platform like MobileDataforce's PointSync Mobility Platform. Why? MobileDataforce and other companies that author mobile middleware and mobile development platforms committ to keeping them current on the latest supported operating systems - so you don't have to. The cost of the operating system updates/upgrades are generally covered in your annual support contract. Companies like MobileDataforce employ legions of software developers who are paid to be experts on mobile operating systems and how to keep mobile middleware and mobile software platforms current and updated.

Palm Treos and Grabba Card Swipers

We are working on a very cool smartphone and mobile software solution at this time. It involves Palm Treos using the Windows Mobile OS and a Grabba Magnetic Card Reader. This allows mobile sales people and route delivery personnel to take credit and debit card orders as they walk through crowds of shoppers, concert goers, delivery routes and outdoor venues.

My team is using MobileDataforce's PointSync Mobility Platform to design, develop and deploy the mobile software solution.

Kevin Benedict Ponders the Future