1. Visualize ALL Your Enterprise Data
From Within SugarCRM
Intricity and Logi Analytics

2. Reporting in Sugar…
• SugarCRM provides easy to
use reporting features and
allows end-users to be able to
build their own reports, and
dashboards
• SugarCRM provides native
reporting capability on data
that resides in the CRM
database

3. 1st Challenge
• Native Sugar Reports can only report on data that
resides in the SugarCRM database
• There are many other sources of data required to
complete a 360 view of:
– customer relationships
– Sales performance
– Vendor
• Other data sources
– HR systems, Payroll, Finance, ERP, EDW, etc

4. One Approach – Load it into the Sugar
Database
• Create custom modules in Sugar to load
the external data into, so that you can
leverage the native reporting capability in
SugarCRM

5. Load the data into Sugar Approach….
Transactional Data Sources
(SQL, XML, etc.)
Web Services
Provider
Data
Warehouse
Metadata
Summary Data
Raw Data
Internet or
Intranet
ETL

6. Challenges with the “Load it into the Sugar
database ” approach….
• The SugarCrm database is designed and optimized
primarily for data entry, and not advanced analytics.
• When aggregating large amounts of historical data and
millions of rows, particularly at the report
level, SugarCRM is likely to experience performance
slowdowns
• SugarCRM native reports are all calculated at run-time.
This can also lead to performance issues.
• SugarCRM reporting while very flexible, doesn’t have the
extensive library of graphic options of specialized
business intelligence tools.

7. Challenges with the “Load it into the Sugar
database ” approach…. (cont’d)
• The viewing of native reports and charts is limited to the
dashboard, and reporting module.
• For organizations that want analytics or KPI’s that are
specific to the customer profile that is being viewed, the
native reporting doesn’t allow charts, and visualizations
to be incorporated into the DetailView for your
Accounts, Contacts, or other records.
• This means that additional clicks are required if you need
to leave the account profile in order to view a graphical
representation of historic sales for a given customer.

8. Depending on the amount of data, type of
data, and complexity of reports…
If you are trying to
make SugarCRM
your enterprise data
warehouse for the
basis of complex
analytics you may be
trying to fit a square
peg into a round
hole…

9. Another Approach – use 3rd party reporting
tool
• Many BI platforms allow for improved performance, and
graphics for performing analysis on disparate systems

10. Challenge with using 3rd party reporting tools
• Separate Reporting tools often create a separate portal
for users to access in order to get at the information.
• When we ask customer facing users to navigate away
from the CRM tool in order to get answers to business
questions, we are essentially with-holding important
information from them until they ask the right question.

11. Salespeople should live in the CRM like a
Goalie lives in his net….

12. Another solution….
Embedded Enterprise Dashboards in Reports within SugarCRM
powered by Logi Analytics
• CRM embedded analytics put the answers
where users are working, so that they are
informed of performance history, and
exceptions within the context of the
business process that they are engaged
in.

13. Why Logi Analytics and Sugar make a good
couple?
• Logi Analytics provides CPU based licenses
with NO PER USER FEES
• Low total cost of ownership
• Quick implementation
• Logi Analytics provides quick connectivity to
multiple data sources in many cases without
the need for a data mart or complex data
extraction and loading
• Huge library of charts, graphs, and gauges
• Easily embedded within the Sugar
interface, and other enterprise applications

14. LogiXML
www.logixml.com
LogiXML – How it works
Logi Info Studio
Transactional Data Sources
(SQL, XML, etc.)
Report Definitions
(XML Files)
Web Server
Web Services
Provider
Data
Warehouse
End User Web Brower
Logi Info
Engine
Metadata
Summary Data
Raw Data
Internet or
Intranet
End User Smartphone or Tablet

15. Sugar-Logi Architecture
15
15
Logi Info Server
Presentation
Engine
Analytical
Engine
Data
Engine
Security
Engine
Logi Info Studio
Develop Deploy
On-Premise
RDBMS
In The Cloud
Web Services Files
Browsers Mobile

16. Data Sources
16
16
Built-in support for a large variety of data sources…

19. Bar Charts

20. Gauges

21. Dashboard Samples

22. Dashboard Samples

23. Dashboard Samples

24. Dashboard Samples

25. Dashboard Samples

26. Two Options for Integration
1. Module specific dashboards, (e.g
Customer Performance Dashboard within
the Account View)
2. Full Integration of Logi Analytics into
Sugar

27. Option 1 – Module Specific Dashboards
• Have a need to incorporate a dashboard within the
customer/account profile so that sales people can see
the performance history while they are viewing the
account record?
• Opportunity success history within the opportunities
module…
• Some other dashboard that requires one of the following:
– Data brought in from outside SugarCRM
– Ability to be viewed from somewhere in Sugar other than the
reports module, or the home page
– A chart, or visual component that isn’t available from Sugar’s
native reports

28. Option 2 – Complete Logi Integration within
SugarCRM
• Replace your native dashboard with one completely
powered by Logi Analytics
• Centrally managed dashboards
• Complete role and security awareness within reports.
– If you’ve blocked access to a certain item using Sugar
roles, then that item will be blocked in the Logi report as well for
that user
• Ability to run Logi reports from the reports module in
Sugar

29. SugarCRM – Logi Analytics
Logi Goes Completely Native within
Sugar
Overview

30. Security
• SugarCRM has several layers of security. Users can be flagged as
system administrators and have access to every module and every
record in the database. Roles determine what modules users have
access to. Using Roles, users can be granted access to every row in
a module without being a System Administrator. Team security
determines what records in the table users can view. The Sugar-
Logi integration takes into account Role and Team security. The
only security feature that is not seamless in field level security. Each
of the security mechanisms are defined below.

31. Logi Report Security
• Security for access to individual reports works a little differently (and
hopefully better) in the integration. When viewing a list of reports in
out of the box Sugar Reports, Sugar uses Roles to determine what
modules you have access to and teams to what Reports you can
see and filters the list of Reports. Since Logi reports don’t have to
be based on a particular module, all of the security is based on
Roles. When the user requests a report or views the
Dashboard, the following occurs:

32. The Sugar-Logi Dashboard

33. Logi Analytics Reports Launched From The
SugarCRM Interface

34. Sugar-Logi Default Homepages

35. Sugar-Logi Integration provides Centrally
Managed Dashboards
Sugar-Logi Integration gives Administrators the ability to create Default Home Pages by
Roles:

36. Thank You
Adrian Boerstra
646-483-4451
aboerstra@intricity.com