Showing posts with label pda. Show all posts
Showing posts with label pda. Show all posts

Mobile Expert Podcast Series: PSION's Mike Petersen, Part 1

I had the pleasure of interviewing PSION's Mike Petersen this week about rugged and industrial grade mobile devices, total cost of ownership and device strategies.  This is Part 1, you can listen to Part 2 of this interview here.  This article is a good one for those debating the merits of using consumer grade smartphones or rugged handhelds for specific jobs and tasks.

When you are done listening to this podcast, I hope you will take a few minutes to complete the enterprise mobility survey.  All participants will receive the survey results in a report for free.





*************************************************************
Kevin Benedict, Independent Mobile and M2M Industry Analyst, SAP Mentor Volunteer
Follow me on Twitter @krbenedict
Full Disclosure: I am an independent mobility analyst, consultant and blogger. I work with and have worked with many of the companies mentioned in my articles.

Mobile Expert Video Series: Electrix's Jeff Morgan

I got to know Jeff Morgan while speaking at the ClickConnect APAC 2011 conference last week in Australia.  Jeff works for Electrix, a company that contracts with utility companies to provide field services, maintenance and asset inspections.  They have a long history of working with mobile applications in the field and he discusses his experiences in this video interview.

Jeff is also the guy that shared the picture of the GIANT snake his colleague saw along the road in Australia.









Upcoming Events

Critical Requirements for Mobile App Development:  Agility and Speed Strategy, Process, and Tools to Accelerate Mobile Development, July 21, 2011
Mobile Tablet Trends in the Enterprise featuring Samsung Mobile - July 28, 2011

Whitepapers of Note

The Business Benefits of Mobile Adoption with SAP Systems
ClickSoftware Mobility Suite and Sybase Mobility Solution
Mobile Adoption Among Gas and Electric Utilities
Mobile Adoption in Life Sciences
Mobile Adoption in Oil and Gas
Networked Field Services

Recorded Webinars of Note

3 Critical Considerations for Embracing Mobile CRM
The Future of Enterprise Mobility
The Latest m-Business Trends and How the Onslaught of Mobile Devices Affects Development Strategies
The Real-Time Mobile Enterprise:  The Benefits of Rapid, Easy Access
Syclo and SAP Deliver Mobile Apps on Sybase Unwired Platform

*************************************************************
Kevin Benedict, Independent Mobile and M2M Industry Analyst, SAP Mentor Volunteer
Follow me on Twitter @krbenedict
Full Disclosure: I am an independent mobility analyst, consultant and blogger. I work with and have worked with many of the companies mentioned in my articles.

In Remembrance of the PDA


How long has it been since you stopped using the term PDA? It occurred to me the other day that the PDA has played an important part in my career and I should not let it pass away without a ceremony of some sort.

The PDA has been replaced by iEverything and smartphones. However, it was an important gadget that paved the way for the mobile technology advances of today. It opened our minds to the possibilities of keeping on task, even with poor memories. It helped generations of soccer moms remember where each child was dropped off and when they needed to be recovered. It allowed us men to seem organized despite ourselves.

PDAs started the concepts of software applications, music and photos in our pockets. PDAs kicked-off companies like Palm and motivated people like me to begin blogging.
Let us be silent for 30 seconds in rememberance of the PDA. We can quietly bow our heads and reach down into our pockets and try to remember the last place we used our stylus before it disappeared.

***********************************************
Author Kevin Benedict
Independent Mobility Consultant, Wireless Industry Analyst and Marketing Consultant
www.linkedin.com/in/kevinbenedict
twitter: @krbenedict
http://kevinbenedict.ulitzer.com/
http://mobileenterprisestrategies.blogspot.com/
***********************************************

54 Questions to Help You Select the Right Mobile Handheld Computer

Mobile computing requires mobile computers. Which brands and models you select can be a hard decision. The following list of questions are designed to help you think through some of the big issues that will enable you to narrow down the selection list.

The first big question you should answer is what is the primary purpose of the handheld or mobile device. Is it barcode scanning, GPS, RFID, surveying, map reading, voice calls, email, digital signatures or field data collection?

The second big question is what is the environment that the device will be used in. Is it used in the office, clinic, warehouse, cold storage or out in the rain on a construction site.

There are a large number of very good handheld computers, PDAs, Tablet PCs, laptops and Smart Phones to select from, however, the key to getting the right mobile device is to research the business purposes and the environment in which the solution will be used before making a selection. The following questions should help you narrow down your list of mobile handheld computers:
  1. What environment will you be working in - is it hot, cold, wet or dusty?
  2. How rugged do you need your device? There is a ruggedness scale.
  3. Are there explosive vapors or explosive powders?
  4. Is it a clean office environment, or a muddy and rugged outdoors environment?
  5. Is the user in and out of vehicles all day?
  6. Is your software application focused exclusively on bar code scanning, RFID reading, GPS, or do you need a multi-purpose data collection device?
  7. Will the hardware configuration ever need to be changed? Some handhelds can be configured at will; others are locked and can only be used with the original configuration.
  8. Will the device be used as a primary phone, or is it focused on data collection?
  9. What hardware requirements does your mobile application require?
  10. Will the battery last long enough to complete your daily work between charges? Do you need back-up batteries? Can you use batteries purchased at the local market, or are they vendor specific?
  11. What is your budget? What does the value of using a handheld computer justify spending?
  12. Do you have enough budget to purchase or develop the mobile software and hardware you need? Does your budget only allow for low cost consumer devices?
  13. How many replacements(of a consumer device) does it take to equal the cost of a ruggedized handheld?
  14. How do you replace broken devices? Can you get a replacement service in 24 hours, or must you wait a week?
  15. What kind of support contracts and warranties are available?
  16. How long will your new handheld computer be supported, serviced and manufactured by the vendor? Is it near end of life and being discounted for a reason?
  17. Can you upgrade the operating system when Microsoft releases a new version of their mobile operating system?
  18. Can you use standard laptop data cards in the handheld, or do you need to pay for high priced vendor specific cards?
  19. Can you view the screen effectively in the sunlight?
  20. Can you add more memory if your requirements increase?
  21. A few industrial handheld computers have flashlights built into the device to provide better light for taking digital photos. Is this useful?
  22. Do you require GPS? If so, how accurate?
  23. Will your users be wearing gloves? If so, small keyboard buttons won't work. How big of keys do you need?
  24. Do you need a water proof, or just water resistant case for your handheld?
  25. Does the bar code scanner work effectively in real-world environment? Some scanners cannot scan effectively through glass or plastic.
  26. Is the size and weight of the handheld appropriate for the user and environment?
  27. Can your handheld computer support all the add-ons you require at the same time? Some devices can only support a specific number of add-on components so you are forced to choose. Some cannot support both a GPS and a data card at the same time. Some devices cannot support both a bar code scanner and a GPS add-on. This is an important consideration.
  28. Do you need only a touch screen and navigation pad, a number pad or a full QWERTY keyboard? This is very important for user acceptance.
  29. Is the handheld device also going to be used as a phone? Is a 2 pound industrial grade handheld really a usable phone?
  30. Does your low cost consumer grade PDA need a rugged case like the ones Otterbox sells?
    If you only have a budget for a low cost device, does it support the battery life and add-on components you require?
  31. How will the device be transported around a job site? Will it strap to a belt, swing from a shoulder strap, sit in a holster or be mounted to the dashboard of your truck? Does your device support your chosen method?
  32. Where is the closest inventory of extra handheld computers? Where is the closest repair depot?
  33. Will your vendor loan you a device on trial?
  34. Can you rent the handheld if you only need it for a short-term project?
  35. Does your vendor take trade-ins on your old handheld computers?
  36. Can you get the same exact handheld, under a different brand name for less?
  37. How will your handheld computer send data back to the office? Cradle sync, WiFi, bluetooth, wireless data card, GPRS/GSM, CDMA?
  38. What size screen do you need? Some devices like the Jett-Eye have a "landscape view" others a "portrait view" many have different sized screens. What do you require?
  39. Do you need an integrated digital camera? Do you need a low or high resolution camera and does your device support it?
  40. Does a refurbished device from Ryzex make better sense that a new device?
  41. Where is your vendor's office? Are they in the neighborhood or on the other side of the planet? Does their location offer you the support and attention you deserve?
  42. Does your handheld computer run on the same operating system that your mobile software solutions requires? I have had customers order Windows CE devices for their Windows Mobile application. It did not work.
  43. Is your device likely to be stolen? If so, you may want to use cheap devices that can be easily secured and replaced. We have implemented projects in Africa where this was an issue for the buyer.
  44. Does your handheld computer come with a pistol grip or other straps that help you avoid dropping it?
  45. Can you comfortably hold the device in your handheld and complete your work? Some devices have scanners on the side, on the end or underneath.
  46. Can you effectively view the data you need? Some jobs simply require a full keyboard and a full screen for viewing large CAD files or Maps. Does your screen size match your requirements?
  47. Where will you store the device when you use the washroom? One of my customers used Tablet PCs and they kept breaking when they slipped off of the sinks in the bathrooms.
  48. Does the mobile device you select support the RFID reader you need for distance and accuracy?
  49. Does the battery in the mobile handheld last long enough after you have added on all the additional hardware accessories? Each added radio uses more energy.
  50. If you have dozens of handheld computers, how will you charge them all at the same time? Do you have a docking station that allows for all of your devices to both charge and synchronize at the same time?
  51. Do you need wireless data plans, or does batch synchronziation after each shift work?
  52. What wireless carrier and data plan provides the best service and cost for you? Does that wireless carrier support your mobile device?
  53. Does the wireless carrier have sufficient coverage for your workers?
  54. What is your budget for each handheld computer? This may limit your selection and make the choice simpler.
I don't sell or represent any mobile hardware. I have just managed many mobile application development projects around the world so have learned some lessons. If you would like to discuss this topic in more detail please contact me.

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

Mobile Application Development Strategies for Handhelds, Smart Phones and PDAs

The mobile application framework on the mobile handheld computer, Smart Phone or PDA can be thought of as a mini-EAI application (enterprise application integration platform). In the world of SAP they have NetWeaver for integrating all of the various applications together. NetWeaver is described as an integrated technology platform. Many different mobile software applications are found on a typical mobile device and they all need to be integrated together as well including:

  • Radios - Bluetooth, wifi, RFID, GPS, Phone
  • Data collectors - RFID, barcode scanners, digital images, voice memos, GPS, credit card swipers, mobile applications and forms
  • Databases, synchronization technologies
  • OS with downloadable applications

All of these various applications need to be integrated together using some kind of mobile integration technology platform. The OS can take care of many of the simple features and functionality, but a database driven integration platform for the mobile device is required if you are going to create various application layers that are all integrated into one downloadable mobile software application that can combine all of the necessary application functionality into one synchronization platform that is integrated with your back-office business applications.

Mobile applications have many unique requirements. Among these requirements are:

  • GUI that can be resized quickly based upon the mobile device used
  • Data collection fields and forms
  • Mobile application workflow engine and validation features
  • Data validation features
  • Framework for pulling in data from third-party data collection hardware and software applications (barcode scanners, RFID, GPS, voice memos, credit card swipers, databases, etc)
  • Mobile database (small databases optimized for mobile devices)
  • Synchronization technology on the mobile device and on a central server

Mobile software application developers will want to find a good development toolkit for efficiently creating mobile applications. These toolkits can assist in quickly creating:

  • Application GUIs
  • databases
  • Synchronization scripts
  • Workflows
  • Integration with third party data collection applications
  • Data validation features
  • etc.

In addition to the basics listed above, it would also be very useful to have the following:

  • Mobile application workflow engine (as described in this article)
  • A mobile software kit based on your back-office ERP or database

Wouldn't it be nice to bring up a "work order ticket" on your Oracle or SAP system and immediately replicate the data requirements and valid data rules on your mobile device database? Today, this is a long and painful exercise. Each field in the SAP or Oracle database for that specific application would have to be analyzed to determine what is a valid data entry. The validation rules, would need to be individually documented and recreated on the mobile application database manually. An ERP centric mobile application toolkit would quickly transfer those data validation requirements to the mobile application that would be collecting the data and synchronizing back to the office.

If you have not developed industrial strength mobile applications before, it may be good to work with some experienced mobile application developers on the first few. There are strategies that experienced mobile application developers employ that can save you much time and pain.

If you would like to discuss this topic in more detail please email me.

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

13 Key Steps to a Successful Mobile Application Development Project

Companies now days are looking for ways to do more with less. Many recognize that their mobile workforce is being managed inefficiently and extending business process automation to mobile field workers is becoming a priority. Saving fuel, reducing paper, reducing administration work load, more efficient dispatches are all important.

The following 13 points identify how you can get started automating and mobilizing these business processes.

Step 1 – Understand the ROI/Scope of the Project and Plan Ahead

“What’s the number one reason a mobile project fails?” is a common question we get asked. The answers are that many companies don’t put enough upfront thought into defining the requirements, scheduling testing resources and planning a deployment strategy. The results of these deficiencies are project scope creep, cost overruns, missed deadlines, poor user acceptance and sometimes even complete project failure.

Step 2 – Build a Team of Stakeholders

Make sure the members of your team have the right roles and responsibilities to help the project succeed. Mobile solutions usually tie into other corporate IT assets and business processes, therefore impacted members of your IT department and business units need to be on the project team.

In addition, a representative mobile field worker(s) should be included on the project team to provide valuable “real-world” insight. Don't forget the folks running the IT helpdesk. They are likely to get called when the mobile handheld PDA runs out of battery, memory or needs repaired or replaced.

Step 3 – Select a Partner That Specializes in Mobility Solutions

Performing successful data synchronization from mobile computing devices can be a challenging and complex task. There are many variables that can affect the results of synchronization. To insure you get your solution done correctly the first time, you need experienced experts in mobile technology. You need technologists who specialize in the design, development, deployment and support of enterprise mobile solutions.

Step 4 – Know Your Target Users

During the planning and scoping phase of your mobile project, take time to experience the working environment of your mobile workers and observe the business processes in action. Pay specific attention to how information is collected and exchanged between the office and the mobile workers. These observations can significantly impact the design, development and deployment of a successful project!

Step 5 - Evaluate the user environment

How do moist, cold and dirty environments impact the mobile devices? How does low light or bright sunlight affect visibility of the screen? Can workers read the small text on the PDA screen, or does the text need to be larger?

Step 6 – Don’t Underestimate the Complexity of Synchronizing Field Data

Step 7- Understand the technical challenges and issues

One of the biggest mistakes a project planner or IT department can make is to underestimate how complex data synchronization can be. Part of designing a solid and reliable mobile solution is to select robust synchronization middleware and to spend time designing and testing the data synchronization. Without the right middleware and design your end users could encounter issues such as extra long sync times (hours, not minutes), duplicate records, incomplete data, lost data and even database corruption. Every one of these issues will trickle down to your support department, so designing it right the first time is very important.

Step 8 – Build in Phases

Most successful projects involve a series of phased implementations. Each phase can be developed, tested and implemented in an orderly manner. Once a phase is deployed and proven, additional phases can be layered on top that include more features and added complexity. Remember, the more data requirements that you add the more data you must synchronize, and the longer each synchronization session will take. Only synchronize data that your remote users require in the field. In addition, most mobile devices don’t have the same CPU power or memory as a PC/laptop, so be aware of how the performance of your solution will be affected by a smaller, lower powered device.

Step 9 – Evaluate Your Hardware and Connectivity Needs

The term “mobile devices” can have many different interpretations. Today, laptops, Tablet PC’s, UMPCs, PDAs and Smart phones are all identified with this term. When determining the best mobile device for your project you will want to consider screen size, data storage capacity, security, physical working environment, required hardware accessories such as barcode scanners, GPS, digital cameras, RFID, and the ability to upgrade the device with updated hardware and software components.How do you connect your mobile device to your enterprise database applications? You have many options including cradle, WiFi, satellite, Bluetooth, wireless, dial-up modems and satellite uplinks to name a few. The method(s) you choose will be affected by how often your mobile workers need to send/receive data. How much data will be transmitted and will they always have connectivity. Study each option, your working environment and consult your mobility partner to make the best selections.

Step 10 – Deploy to a Limited Focus Group, Evaluate and Improve

Once you have completed version 1 of your mobile solution and you are ready to deploy in the real world, roll out your solution to a small group of trusted and motivated users. Define a specific period of time to evaluate the solution, document the results and identify any required changes and improvements. The result of this evaluation should be an improved mobile solution that is ready for wide deployment.

Step 11 – Set and Enforce Hardware and Security Policies

Mobile devices are small computers with the ability to store sensitive corporate data, communicate this data over the Internet and even catch viruses. You must clearly communicate how mobile devices are to be used and for what purpose. Establish and publish guidelines for using mobile devices.

Step 12 – Provide Full Support for Mobile Users

Mobile devices are guaranteed to break. What is your plan for keeping a mobile worker productive and communicating business critical information when their mobile device ceases to function or gets misplaced? These are inevitable issues that are best planned for in advance. Have a plan and a documented back up process.

Step 13 - Select a technology partner that understands your business applications and ERP

I f you use SAP, make sure that the mobile technology partner you select is also an expert in SAP mobile.

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

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:
  1. Who does the field worker call if there is a mobile device problem?
  2. Who does the field worker call if their mobile application is not synchronizing correctly?
  3. Who trains new employees on how to use the mobile device and application?
  4. 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?
  5. Who does the field worker call if the mobile application needs edited or upgraded?
  6. If the user downloads a new version of the mobile operating system and the mobile application doesn't work, who will fix it?
  7. How do you prevent mobile users from downloading new software applications that might break the system?
  8. How do you back-up mobile devices so the information is centralized?
  9. Who owns and defines the business process you have mobilized? They may need to approve any changes to the business process.
  10. Who controls the security of the device?
  11. How do you set-up a new user to securely access the enterprise database?
  12. What kinds of security rules must the field user follow?
  13. Do different users have different security profiles?
  14. Is there a standard set of security rules for mobile devices across the enterprise?
  15. Who controls access to the enterprise database application (a DBA)?
  16. 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.
  17. Are synchronizations done in real-time, near-real-time, or batch on a schedule?
  18. Does one mobile device have multiple synchronizing applications? Are they on different schedules or do they synchronize at the same time?
  19. 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?
  20. 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?
  21. 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?
  22. Do different job functions require different devices, carriers and wireless data service plans?
  23. Who decides what brand of mobile devices are going to be the company standard?
  24. 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?
  25. 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?
  26. Are the mobile devices or the mobile software solutions under warranty? Where are these contracts stored? Who owns them?
  27. Is there a yearly support contract IT needs to know about? How much? Whose budget?
    What is the account number the warranty is under?
  28. 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?
  29. 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?
  30. 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?
  31. 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?
  32. 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.
  33. 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?
  34. How do you disable synchronization on a lost or stolen mobile device?
  35. How do you kill and/or protect your data on the mobile device if it is lost or stolen?
  36. 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?
  37. 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.
  38. 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?
  39. 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?
  40. Some mobile projects require different levels of security, for different levels of data visibility. How would you manage and track that?
  41. Will your company standardize on 1 mobile operating systems or several (Blackberry, Microsoft Windows Mobile, Palm, Android, iPhone, etc)
  42. 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?
  43. 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?
  44. 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?
  45. Does your mobile device reseller have a replacement program?
  46. 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?
  47. 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?
  48. 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?
  49. 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.
  50. 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?
  51. 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)
  52. 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?
  53. 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?
  54. 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?
  55. 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?
  56. Who determines the hardware requirements that support the mobile application and desired synchronization speeds?
  57. 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?
  58. 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?
  59. How does the IT Helpdesk know which one of the 17 mobile applications on the handheld computer is having a synchronization problem?
  60. 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?
  61. 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.
  62. What wireless carrier, technology and through-put speed is the mobile device using? Is it GPRS, GSM, CDMA, Edge or some other network configuration?
  63. 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.
  64. What do you do with old and retired mobile handheld devices? Companies like Ryzex buy back old handheld mobile devices and recycle them.
  65. What rugged or semi-rugged cases are required to protect the mobile device?
  66. 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?
  67. Does the same mobile software application work on rugged mobile handhelds and on mobile consumer devices?
  68. What employees and roles get the different levels of rugged devices?
  69. 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
***********************************************

Mobile Software SDKs and Toolkits for Handheld PDAs and Smart Phones

In the recent article by Peter Wayner of InfoWorld called iPhone development tools that work the way you do, he describes the value of using a mobile application SDK or framework. He lists 4 new toolkits to help mobile application developers develop applications faster for use on handheld PDAs and Smart phones. This is a market in which I am intimately familiar.

The challenge with the market for mobile application frameworks and SDKs is that very few developers want to spend money on an SDK from a small vendor, and even fewer companies want SDKs or are willing to fund long term custom development and support projects internally. Companies want a finished product that works with their ERPs, database and accounting applications. They don't want to invest in a non-standard mobile framework. They want mobile extensions to their enterprise applications. SAP is addressing this with their NetWeaver based mobile infrastructure. This provides SAP users with a standardized method for extending their applications out to mobile devices, but it does not address how to develop the mobile application code. This theoretically creates an opportunity for mobile SDK vendors.

Appforge and Dexterra are two very BIG examples of how challenging it is to be a successful vendor of mobile application frameworks and SDKs. It is yet to be proven that there can be a successful business model as the author of these mobile application frameworks, unless you are a giant like Microsoft or Apple. Dexterra bet the house that Microsoft would acquire them and they lost.

Now, it is true that to make these finished mobile software applications, there is a need for powerful mobile SDKs, but these SDKs are very costly to development and there is yet to be a good and proven business model for small independent vendors of such.

Some vendors of mobile application frameworks want to sell you a toolkit and then charge you a license fee for every mobile device you deploy on. This is not a good model, unless the application is an off-the-shelf mobile application. It makes sense to pay for syncing technology and mobile databases, but a per deployment model for code that you create is hard to swallow.

The biggest challenge vendors of mobile application frameworks and mobile SDKs face is getting the economies of scale that all software companies seek. Who is the real market? Developers? They seek to work in the sexy high profile technologies from the big name companies so they can pad their resumes. They do not want to take a chance on learning an SDK from a very small company that no one knows and they are unlikely able to leverage in the future. They may use an SDK to deliver their cool mobile application, but there is simply not enough of these developers willing to buy your SDK for significant amounts of money to be profitable.

Does the IT department in a company want to buy your SDK, a few but not enough to build a profitable long term software business as an SDK vendor. Again, companies will always seek a finished mobile application that extends their internal IT investment. If SAP has a mobile framework, they want that. If SAP didn't have the mobile extension, then the company would want a finished mobile application that is already integrated with SAP.

In summary, there are many examples of companies developing very cool mobile SDKs and mobile frameworks, but very few with successful business models. Companies want to extend internal applications with mobile extensions developed by the owner of their internal applications. In the event there are no mobile extensions from their key vendor, then they want a finished mobile application that is pre-integrated with their ERP or back-office applications. SDKs are cool, but a successful business model remains elusive.


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

Rugged iPhone Cases for Mobile Workers



The iPhone is a beautiful mobile device. The recent software announcement by TomTom turns the iPhone into a turn-by-turn navigational device. Barcode software that utilizes the camera in the iPhone converts it into a barcode reader. Mobile software applications are being uploaded to iTunes weekly for the iPhone that provide companies with an increasing number of business applications. However, none of these cool software applications help the iPhone survive in the rugged outdoor working environment.



Last week I went into a store that specializes in Apple products. It is the closest thing to an Apple store that we have in downtown Boise. On the rack I saw a ruggedized case for an iPhone from Otterbox. I got excited!



I have been working with Otterbox cases for years in the context of PDAs and mobile handhelds and have always very impressed with how they can engineer rugged cases so precisely. Most are water resistance, padded and dust proof. These are all great steps in the right direction. The Otterbox case provides a flexible soft plastic screen to protect the iPhone but still allows the touch screen to work well.

If you can't leave home without your iPhone, but you either work in rugged locations or enjoy rugged outdoor activities, you may want to make the investment to protect your precious.

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

Mobile Workflows in the Field, SAP and Other ERPs


The way business processes are designed, implemented and standardized within a company can often mean the difference between success and failure. If often takes years of trial and error, and sometimes flashes of brilliance to come up with just the right business process that will mean success and competitive advantages.

Once the perfect business process is proven it needs to be implemented and automated. Why automated? Because humans are forgetful and have even been known to be from time to time lazy. They want to cut corners and avoid that which is tiresome. Automation enforces and manages the perfect business process.

For years software vendors and ERP developers like SAP have developed applications that help design workflows and workflow engines to run them. These provide the technology infrastructure within the enterprise to automate these business processes and to ensure they are followed, however, once an employee exits the building and drives away in a company van to perform a task remotely, the automated business process breaks down. Suddenly, the business processes that you have spent years perfecting are useless. The employee has broken the "connection" and walked out the door to freedom.

Even today, most mobile field service workers leave the building with a clipboard and a stack of paper service tickets or work orders. How they perform their work, in what order and the processes they utilize in the field are now unsupervised and up for interpretation. The field service technicians often don't much care for the business processes designed by the teams of MBAs in suits at the office. They have their own preferences and opinions about how things should be done, and in remote jobsites who is going to argue?

Many large companies have up to 40% of their employees working remotely and/or in the field on jobsites. How can the SAP or other ERP Business Process Expert design and implement business processes that can be utilized and enforced in mobile and remote locations? This is a challenge worth resolving.

Think about it, a company pays tens of millions of dollars implementing SAP internally and designing business processes and workflows to operate their enterprise. Yet for many services based businesses the money is earned outside the office at remote locations. The location where the customer interaction takes place and where the money is made is often devoid of best in class business process automation.


Mobile applications that need to synchronize with ERPs, should implement mobile workflow support. This requires a client server architecture whereby the mobile client software understands that a workflow or event manager is associated with a particular process and the server also understands that it is both producing and consuming data with the mobile device that is part of an event or workflow. Let me provide a scenario.


A service technician has a ruggded PDA or other mobile device on his belt. He receives an alert that he needs to be dispatched to a jobsite. This initiates a business process with a workflow associated with it. A series of tasks that make up the dispatch and completion of a service ticket are now initiated. The tasks may include:



  1. Dispatch receives a service call

  2. This initiates a series of tasks including estimating the availability and analyzing the location of all service technicians in the area.

  3. Once the nearest available service technician is identified a service dispatch can be sent

  4. Service technician confirms availability and accepts the job

  5. Least cost and fastest routing information is sent

  6. Service technician arrives at the jobsite and pushes a button on his mobile device annoucing his arrival.

  7. Arrival message synchronizes with the server workflow or event manager notifying dispatch of his location on site.

  8. The workflow may include an inspection, detailed findings, proposed solution, repair and collection of the fee

  9. Any parts needed will be automatically deducted from the service vehicle's inventory

  10. The workflow can also include sales and marketing activities such as promoting an Annual Service plan or equipment upgrade to the customer

  11. The repair is complete, dispatch is notified

  12. The service technician is available for another job

In this scenario, the mobile client application using a workflow engine that interacts with the server side application steps the service technician through the various tasks included in the business process. These steps can be directions in the form of alerts, messages, next steps, data fields that require input, and feedback from the dispatch office. Each step of the workflow required input from the service technician to confirm that the step had been completed and this information was in turn synchronized with the server side workflow engine. This enables the best practices supported by the company to be practiced and supervised in the field.


SAP has a solution called Event Manager. It is designed to manage activities happening across a geographically dispersed supply chain. It requires data input via B2B and EDI data communications. Similarly, mobile applications can feed data into a centralized workflow or event management solution that helps support and ensure best practices across remote jobsites.


A workflow engine and a mobile client version of a mobile workflow engine is required by companies that want to standardize business processes in the field where interactions with customers take place and where revenue is earned.


If you would like to discuss this concept in more detail please email me.

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

Mobile Software Applications, Supply Chains and Medicine Delivery


When a person typically associates mobile devices, iPhones, Smart Phones, PDAs and other hand held computers with medicine they envision a medical clinic or a hospital environment. However, mobile handheld computers and medicine are also used in remote locations and in medicine supply chains that you may not have thought about. Let me first share an article I read this week that describes some of the challenges incurred while delivering medicine in Brazil.

Armed raiders attack medicine shipments in Brazil

Author - Phil Taylor 27-Jul-2009

A delivery truck carrying medicines was attacked by bandits in Sao Paulo, Brazil on July 19, resulting in a heavy exchange of gunfire with armed escorts. There were no fatalities and the raiders failed to make off with the shipment, which was valued at around $530,000 and contained products from several different companies, according to information received from pharmaceutical industry sources.

The bandits, in two vehicles, forced the driver to open the truck door at gunpoint. That triggered an alarm which informed the transport firm that there was a problem with the shipment. The escorting vehicle’s guards pushed the panic button and responded to the criminal’s opening fire, while other escorting vehicles patrolling the same route joined the fray and eventually drove the thieves off.

A similar attack, involving the same transport firm, took place in Brazil in June, and in this case one of the security guards was injured in the exchange of gunfire.
~~~
Note the mobile device that monitored the doors and automatically reported a breech of security.

Talk about a supply chain and logistics challenges! YIKES!

I had the good fortune of working on a mobile software project where we developed a mobile solution that helped track, monitor and report the location and inventory levels of medicine being delivered around the world. The donor organizations, needed to have visibility and accountability that the medicine they donated actually reached the intended destinations and patients.

This mobile software application used consumer grade Smart phones with bar code scanners and wireless connectivity so the boxes of medicine could be scanned and their location and inventories in Africa could be reported to the organization's headquarters in Washington DC. At headquarters all the donor organizations could access the database and generate reports on the delivery and use of the medicine.

Here is another interesting article you may want to read about mobile applications in the Coffee and Espresso product supply chains.

If you would like more details on these mobile applications email me.

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

Motorola's MC55 Handheld PDA


Motorola recently announced a very intriguing new handheld PDA called the MC55. Here is what Motorola says about it:

MC55 Enterprise Digital Assistant (EDA)

The MC55 EDA brings a new level of flexibility, functionality and rugged design to size-optimized mobile devices, providing mobile workers with the power to streamline business processes, increase productivity and improve customer service. The smallest and lightest Motorola rugged EDA with a 3.5-inch display, the MC55 packs the power of a cell phone, two-way radio, bar code scanner, digital camera and mobile computer — all into a single device. Designed to meet mobile worker, business application and IT requirements, this easy-to-use and easy-to-carry business-class device offers true consumer styling as well as enterprise manageability, security and scalability.

Note the emphasis on extending business processes, business applications and its rugged design. I like it!


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

Good Technology, Vendor of Mobile Sync for Handheld PDAs is Sold Yet Again

It is not easy being a mobile synchronization technology vendor. Synchronization is a technology category that is about as sexy as the kitchen drain pipe. Yes, it is needed, but do you want to schedule a board level meeting and use up precious IT budget on it? Obviously not many companies. For the second time in 2 years Good Technology was sold and the price goes down each time.

"Mobile push synchronization platform and service provider Visto acquired Motorola's Good Technology Feb. 24. Motorola acquired Good in 2007 for more than $400 million in hopes of challenging Research In Motion's dominance in the enterprise mobile e-mail market. "

[Opinion Alert] People get excited about cool mobile gadgets, PDAs, Smartphones and manly rugged handhelds with integrated GPS, digital cameras and powerful mobile software applications that make their work and life easier and more enjoyable in an obvious way. The problem with synchronization software is that it is the drain pipe and no one cares about it unless it doesn't work. [/End of Opinion Alert]

"We believe that this transaction is in the best interest of our customers, employees and shareholders," said Gene Delaney, president of Motorola's Enterprise Mobility Solutions. [translation] No one was buying it.

When an individual purchases an iPhone, do they walk around the Apple Store with the hip, pierced and scruffy-faced Apple nerd pondering the merits of various synchronization technologies? Of course not! They want the cool smartphone to work and they want the provider of the device to figure out synchronization. That is Apple's and AT&T's strategy (and most others) and you can see this strategy in Google's recent license agreement with Microsoft for their Activesync. Google, with their growing suite of mobile applications, are hiding synchronization in their cloud computing environment. It is just there and available. The user is not spending a lot of time thinking about it.

Perhaps that was Motorola's original plan. but Good Technology was competing with RIM's world of Blackberrys, Microsoft and Apple. That is not a list of competitors I would want to be facing and betting $400 million against. I must say that the person behind that purchase must have studied Dale Carnegie's "How to Win Friends and Influence People" and took it to heart.

Good luck Visto!
***********************************************
http://mobileenterprisestrategies.blogspot.com/
***********************************************

Windows Mobile Rugged Handheld PDA the i-Mate 810-F


For those of you involved in the mobile handheld PDA industry you know that there is usually a distinct line between the categories of rugged industrial grade handhelds and the category of consumer grade mobile devices such as Smartphones, PDA Phones, iPhones, etc. It only takes a few questions about the environment the customer is working in to make a recommendation as to the kind of mobile device required. That process is now getting harder as the announcement below demonstrates.

"i-mate, the global specialist in Microsoft Windows Mobile devices and software, today launched the i-mate 810-F, the world’s first complete lifestyle mobile with a lifetime warranty. Designed to meet military specifications, the 810-F combines high-end mobile technology and incredible durability in a single sleek package. Whether you work in the great outdoors or in an office, on the road or on a building site, or you just simply want a tough take-anywhere mobile, the 810-F offers everything you need for work and play. The phone comprises waterproof rubber casing and exposed metal screws to lock in the factory seal, making it impervious to almost anything. A full QWERTY keyboard, and impact resistant touch screen, means you don’t miss a thing while you are out and about... The 810-F is designed around the stringent MIL-STD-810F series of standards. These standards are issued by the U.S. military’s Developmental Test Command, a body whose role is to ensure equipment can withstand the rigours of the most extreme environments. This means the i-mate 810-F can cope with pressure, heat, water, humidity and even extreme shock without missing a beat. The 810-F is equally happy at a chilly -10°C or sweltering 60°C, and can be fully submerged in water."

How do you select the right rugged handheld, Smartphone or PDA? This article on the site called Mobile Software & Handheld PDA Business Strategies has a chapter called Selecting the Right Mobile Computing Device for the Solution.




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

Questions to Ponder before Starting a Mobile Software Development Project for Handheld PDAs, iPhones and Smartphones

This article identifies some basic questions that should be asked and pondered by the business user and software development teams before starting on a mobile software development project:
  1. Do you anticipate needing one mobile software application, or many? Can you start with a mobile software development platform that supports all of your mobile application needs, or will each mobile application be a separate IT project and use different development technologies and infrastructures (e.g. Windows Mobile, Google Android, RIM Blackberry, Symbian, iPhone, etc.)?
  2. Do you know your exact solution and data requirements in advance? Do you anticipate needing to edit and adjust your mobile application as you learn from your field users and their experiences? Can it be hard coded, or does it need to be flexible and easily edited? The answers to these questions will impact both design and schedules.
  3. Do you have an in-house software development capability, budget and helpdesk infrastructure to enable you to develop and support your own mobile application(s)?
  4. Are you going to outsourcing the development of your mobile software application's design, development and deployment to an experienced mobility company, or build it internally?
  5. Will you be synchronizing your field data with one back-office database, or multiple database applications? How will you do this? Are you using a middleware solution in this process?
  6. Do you know how to integrate field data to your database applications? Do you have your own DBA that can do this? Are they involved in the data synchronization discussions. How can you ensure valid data is synchronized from the field?
  7. How secure does the mobile data synchronization need to be? The more security that is added and layered the slower the data synchronization. Does only a small part need to be secure or all of the data?
  8. Will the user always need and have internet connectivity, or will the application run equally well disconnected? Does you design take this issue into consideration?
  9. Mobile solutions are often used on laptops, Tablet PCs, Smartphones, PDAs, and rugged handhelds. Do you know your hardware requirements and user environmental requirements? Is the user environment hot, cold, dry, wet, dusty, flammable or frozen?
  10. Will you be supporting just one mobile device, or many different kinds and sizes? Is the screen size an issue? What size is the screen on your chosen devices? Is it sufficient for the work done in the field. Does the mobile worker need to read manuals, maps, images, blueprints and drawings, or just click on a few buttons?
  11. What mobile device operating system(s) will you be supporting?
  12. How will the mobile handhelds or mobile devices be carried and stored. Is the user wearing a suit, or wearing overalls in the rain. Does the environment require a rugged case, or a suit pocket? The answers to these questions impact your choice of mobile devices, operating systems and screen sizes.
  13. If your internal IT staff are developing your mobile solution, do they know how to do the following: integrate with and support GPS, Barcode scanners, RFID radios, Digital Signatures, digital cameras and synchronize data bi-directionally across multiple databases?
  14. What mobile database will you use? Does it have its own synchronization technology? If not, what mobile middleware are you going to use? Does the mobile database vendor support the operating systems you have chosen?
  15. Do you have an IT development team that is experienced in designing, developing and deploying mobile applications, or is this their very first mobility project. Can you afford the steep learning curve, time and money developing a mobile application in-house with no experience?
  16. Have you considered the implementation, training and support effort required to manage large mobile software deployments? Do you have project management and helpdesk software in place to manage it?
  17. Have you made sure that your mobile software application's database and screen design will include the data fields required by the office database application you will sync with?
  18. Does the mobile software application need to support a specific business process in SAP or other ERP? Have you designed the mobile software application to do so?
  19. One of the most challenging and complex parts of mobile application development is to create the right data model for your mobile application before you start development. Often an appropriate data model for a simple mobile application, is not the appropriate data model once you start adding features and additional modules in future versions. Is your database model designed to easily support additional components?

These are a few of the questions you will want to discuss with both the business and the technical team before you begin this effort. For more questions and possibly some answers you may want to visit this Google Knol called Mobile Software & Handheld PDA Business Strategies.

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

PDAs and Handhelds Used for Medical Research Projects in Peru

In this article the use of handheld PDAs on a medical research project in Peru is detailed. The handhedl PDAs provided the following benefits:

  • reduced delays
  • reduced errors
  • reduced workload
  • reduced the time it took to process medical data by 15 days
  • prevented lost data
  • patients could be monitored in a more timely manner
Here are the details of the study and the use of the handheld PDAs as was detailed in this article in the article at ITExaminer.com Patients with drug resistant tuberculosis undergo a two year regime of powerful antibiotics, including injections six days a week during the first six months, with monthly testing. The test results dictate the course of treatment. The half-month delay in getting information from the outback to the city medical facility disrupted the treatment plan.

Here is a description, as described in this article in the Hindu News, of the patient record process before the use of handheld PDAs -

Under the old patient tracking system, a team of four healthcare workers would visit more than 100 health care centers and labs twice a week to record patient test results on paper sheets. A couple of times a week, they returned to their main office to transcribe those results onto two sets of forms per patient — one for the doctors and one for the health care administrators.

From start to finish, that process took an average of more than three weeks per patient. In some extreme cases, results were temporarily misplaced and could take up to three months to be recorded. There was also greater potential for error because information was copied by hand so many times.

Collecting of data in the field and synchronizing the data to a centralized database application for immediate storage and analysis reduces the need to manually retype all of the information and eliminates time delays that may cause treatment problems. Re-typing data from paper forms introduces more errors in the data and increases the workload for clinicians, so avoiding those issues by using handheld pdas for data collection and synchronization was found to have many benefits.

Additional news articles on the use of handheld PDAs in remote locations in healthcare can be found here.

The Power of Digital Cameras on PDAs, Handhelds and Smartphones

In this morning's newspaper there was an article called, "With New Smartphones, Doctors Reinvent the House call." The article relates how a Doctor can use a smartphone, PDA or other handheld computers to quickly view x-rays and give advice remotely. Other applications mentioned were for perusing pharmaceutical libraries and for showing educating patients with anatomical drawings. Although each of these applications are useful, I believe the real power comes from the ability to remotely collaborate with other team members that can all look at the sames information, in high definition and exchange real time data and thoughts. It is amazing what can be accomplished with these new mobile devices.

Digital Cameras in handhelds, PDAs and smartphones are becoming very powerful tools. Today, Sony Ericcsson announced they have included a 12 mega pixel camera in one of their new smartphones called the Idou. In the context of the healthcare field you can image how useful 12 mega pixel photos can be to healthcare professionals where clarity of x-rays, ultra-sounds and other images are critical.

There are many other uses for powerful cameras, crystal clear images and high speed data connections. In the context of the military or field engineers, they ability to see clear satellite images of objects on the ground is very important.

Several years ago I worked on a mobile project for the state of Washington in the USA. They were doing erosion surveys around rivers and creeks. They could do in-depth studies on river erosion from satellite images, but in designated areas they wanted to look at particular events on the ground. Rugged handheld computers with excellent screens and clear photos allowed them to quickly identify objects and geological events on the ground that required a closer look. The GPS coordinates led them to the exact location and then clear photos helped them survey specific areas.

The ability to move data, in real time, from office computers and database applications to mobile devices is a complex task. The ability to quickly develop custom mobile applications that provide you with both data collection capabilities and the synchronization of data from the office takes special technology developed by companies such as MobileDataforce and others.

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

Ericsson Turns to Navigation for Mobile Handheld PDAs and Smartphones

In an article in today's Wall Street Journal called Ericsson Turns to Navigation it is reported that Ericsson is looking at navigation applications with voice commands as an revenue stream for their carrier partners. Everyone is getting into the act because the bigger screens on smartphones and mobile handheld PDAs like some lines from Ericsson, Blackberrys and iPhones make it easier to see maps and read directions while on the move.

Navigation applications and data for consumers will be quickly followed by applications designed for businesses. Navigation and voice directions can be integrated into delivery, work order and inspection applications on mobile handheld PDAs.

Google has already created consumer oriented applications for iPhones that let friends know where friends are on a map. It won't be long until businesses can also see the location of their employees, job sites and company vehicles via PDAs, handhelds and Smartphones. Google makes this application free. I believe applications like this will quickly become available as widgets or gadgets that any software developer can quickly add to their mobile application.

It is a fun and exciting time in the mobile handheld PDA technology world.

Comparing Netbooks, Mini-Notebooks, PDAs and Handhelds in Field Services

I am a big fan of Netbooks and Mini-Notebooks. These are lightweight portable computers generally with 7-inch to 11-inch screen sizes optimized for internet connectivity. They often have exceptional battery life and can be used as a truly convergent device. Often they are optimized to run the complete Microsoft Office Suite. This article discusses them in more details.

The term Netbook refers to the fact that they are optimized to work on the internet. They are mobile internet devices that also have the power to run your standard office software applications. Doesn't most mobile handheld devices and PDAs that run Windows Mobile already provide these functions? Yes, but the 7"-11" screen is a vast improvement, especially for people needing to do real work, process and read large amounts of data and read diagrams, maps and drawings.

The Netbook, as a mobile internet device, should be set-up to access online documents, manuals and work order applications through simple internet logins. These devices can be generic enough to be shared by a complete workforce. In the morning the user can simply check out a Netbook, login and have access to all the information they need in the field.

Let's take the example of a service technician in the field. A small mobile phone is just not a good option for comprehensive work order management. It will quickly kill the eyes of the user. You need a bigger screen to work with any kind of data intensive work orders or parts catalogs. At the same time, you do not want the bulk and weight of a full size laptop. A small Netbook with a 7 inch screen can fit in the pocket or in a padded pouch easily. The screen size is big enough to show a lot of information and data fields without constant scrolling.

In situations where internet connections will be intermittent you may want to consider a work order management system that can function equally well connected or disconnected and use database synchronization in the background. Vendors like MobileDataforce specialize in these areas.

SAP, Landis+Gyr, Electrical Utilities and Mobile Handheld PDAs

SAP, the world's leading provider of business software, announced yesterday a new partnership with Landis+Gyr, a leading provider of integrated energy management solutions. This partnership includes a software development agreement for the integration of Landis+Gyr's advanced metering infrastructure with the SAP® for Utilities solution portfolio using enterprise services.

You are seeing SAP recognize that there are many specialized business processes that are needed beyond their core ERP solutions, and outside the four walls of the office in mobile environments. SAP has been seeking partnerships that address the industry specific business process needs of companies with mobile workforces.

So far, SAP has seemed willing to give up the mobile applications market for PDAs, handhelds and rugged mobile computers to third parties, and restrict themselves to developing APIs and enterprise service integration repositories for specialized third party mobile application companies like MobileDataforce and others.

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

Interviews with Kevin Benedict