Mobile Cloud Solutions for SugarCRM - Connecting Your Field Force - Anywhere | SugarCon 2011


Published on

What are the practical requirements for a mobile CRM solution? What does your field force demand - and expect? How do you mobilize large quantities of CRM data, offline, and maintain performance? How do you deal with the inevitable variety of device platforms in the field? The practical challenges of meeting employee expectations in relation to performance and availability are explored in this session, which draws on a decade of mobile CRM solution development and operation. Examples of a specific SugarCRM solution on several mobile platforms are shown to demonstrate best practice in action.

Presented by Chris Hall, Commercial Director, LogicAppeal, at sugarCon 2011

Published in: Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Mobile Cloud Solutions for SugarCRM - Connecting Your Field Force - Anywhere | SugarCon 2011

  1. 1. Mobile Cloud Solutions for SugarCRM<br />2011 SugarCRM Customer & Developer Conference<br />Connect your Field Force – anywhere! <br />
  2. 2. Introduction<br />SugarCRM Solutions<br />Mobile Solutions<br />SAP Business One Solutions<br />
  3. 3. Mobile Credentials<br />12-years mobile solutions experience<br />Device specific development<br />Palm<br />Windows Mobile<br />Device agnostic development<br />Rhodes<br />All on-line/off-line solutions using synchronisation<br />“Mobile”<br />
  4. 4. The Cloud<br />A provider's offering of abstracted Internet services is often called "The Cloud”.<br />Cloud computing is a general term for anything that involves delivering hosted services over the Internet. <br />RhoLogic operates a Private Cloud to deliver RhoLogic Mobile for SugarCRM as Software-as-a-Service (SaaS) <br />
  5. 5. Requirements<br />Based on mainstream requirements from field staff or management during 12 years of mobile development and operation<br />What is the need and what does that mean?<br />
  6. 6. Field Force Requirements<br />Need<br />Solution<br />Availability and speed of operation<br />Off-line access. Provides for improved device interaction and counters Internet absence in regional areas, inside buildings, etc.<br />Off-line data volumes<br />CRM’s can contain significant data volumes. Challenges exist to achieve device performance when managing and retrieving data and initial data load.<br />Not all employees have the same device. We need to accommodate choice (BYOD), ideally from a single code base.<br />Mix of devices (BYOD)<br />Customisation<br />Create a single application that adapts in real-time, with a single code base, to both Studio and Module Builder customisation.<br />Total solution therefore is a combination of on-line/off-line operation, capable of handling high volumes, running on several device types, with a dynamic, adaptable framework using a single code base.<br />
  7. 7. Solution Requirements<br />Customization implies metadata. There is no point knowing what to show if we don’t know how to show it.<br />Offline implies local data. Local data has to get there/be maintained. 1Gb of data is tough on Blackberry with a 2.8 Mb browser limit.<br />Cross-platform and single code base implies standards. Browser is the key. Browser rendering handles device interpretation.<br />
  8. 8. Architecture Requirements<br />Private Cloud, Multiple Tenants<br />Suitable for clients that have small numbers of users and cannot justify their own private environment.<br />Synchronization platform is hosted. This connects to each client’s SugarCRM instance. Devices in turn connect to the synchronization server.<br />Sync<br />Private Cloud, Single Tenant<br />Suitable for clients that have larger numbers of users or have a security requirement/desire to be segregated.<br />Synchronization platform can be hosted or on premise. Connection as per multi tenant example.<br />Sync<br />
  9. 9. Development Requirements<br />Major cross-platform development frameworks.<br />Tools such as these required to develop using a single code base.<br />Rhomobileonly framework to offer synchronization.<br />
  10. 10. Comparison<br />How do 3 mainstream solutions compare in terms of requirements demanded by the field force. Where are the differences?<br />How do the mainstream solutions compare?<br />
  11. 11. Solution Comparison<br />SugarCRM<br />iEnterprises<br />RhoLogic<br />Offline<br />N/A<br />Bulk Sync<br />Device Mix <br />Customization<br />
  12. 12. Our Solution: Rhologic<br />iPhone<br />Blackberry<br />Android<br />Sales<br />Support<br />iPad<br />Accounts, Contacts & Leads<br />Accounts, Contacts & Cases<br />Opportunities, Quotes & Products<br />Tasks & Notes<br />Calls, Meetings, Schedule<br />Calls, Meetings, Schedule<br />
  13. 13. Demonstration<br />
  14. 14. Contact Details<br />RhoLogic<br />Level 1<br />12 Waterloo Road,<br />North Ryde, NSW 2113<br />Australia<br />Phone: +61 2 8090-7312<br />Fax: +61 2 9887-4010<br />Web:<br />Email:<br />