Breaking Free of Big BI: What's Possible in Embedded Reporting

Post on 19-Jun-2015

328 Views

Category:

Business

0 Downloads

Preview:

Click to see full reader

Transcript

Breaking Free of Big BI: What’s Possible in Embedded Reporting

featuring Origami Risk

7900 Westpark Drive, Suite T107 McLean, VA 22102 | www.logixml.com

• Introduction (David Abramson, Director of Product Management, LogiXML)

• Limitations of Big BI

• Case Study: Origami Risk (Steve Fischer, CTO, Origami Risk)

• Choosing the Right Vendor

• Wrap Up and Q&A

Agenda

2

LogiXML

• Founded in 2000

• First to market with web-based BI

• Headquartered outside Wash. DC• Offices in Los Angeles and UK

• High customer ratings in Gartner BI Platforms User Survey• Software & Support Quality• Overall Customer Experience

• Over 500 customers worldwide• Over 50% are ISVs and SaaS companies• 10-year-old dedicated OEM practice

3

• Faster Time to Market

• Maintain Your Focus

• Win Faster and More Often

• Increase Customer Satisfaction and Retention

• Create New Revenue Streams

Why Embed Dashboards & Reporting?

4

Origami Risk Case Study

5

• Startup founded in 2008

• Innovative provider of a full-featured risk management information system (RMIS)

• More than $1 million in revenue within 2 years

• Known for:• Claims, incidents, and policies management• Values tracking• Reports and analysis• Risk dashboard• Data update

Origami Risk

6

• Consolidate risk data and use tools to understand risk, identify cost drivers, manage risk events, and share risk data and analysis across the organization

• Powerful features and easy to use

• Best-in-class risk management technology

• Reporting is a key component of the product’s value

• Deployed on the Cloud

Risk Management Information System

7

• Crystal Reports

• Business Objects

• SQL Reporting Services

• LogiXML

Vendor Evaluation

8

• Highly flexible UI for filters and levels of groupings

• Embeddable within our application, not just a report module

• Interactive dashboard capabilities

• Extensible via a plug-in to do hardcore manipulations behind the scenes

• Lowest overall cost

Why LogiXML?

9

• Entered the market with a viable product <6 months

• 10 report templates (now have 50)

• 10 dashboard panels (now have 35)

• Plug-in that extends Logi’s capabilities with a UI for non-technical users to do powerful analytics

Implementation

10

Demo

11

• Fast time to market with a profitable brand new product

• Strong customer response: reporting and dashboard components are a real showcase for the product’s value

• Enabled hardcore analytics that regular people can use through extended UI plug-in

Results

12

• Extensibility and flexibility

• Integration—security and white-labeling

• Ad hoc capabilities/interactivity for end users

• Data source and web browser neutrality

OEM Software Requirements

13

• Flexibility and Robustness• Meet customer requirements today• Grow into future needs without losing your investment

• Time to Market• Different vendors have different expected implementation periods• Need to get things up and running within or a few months or less urgent?

• Maintain Your Focus• Factor in the resources required to build and maintain over the long term• Let the vendor be the BI expert while you focus on your core business

Choosing the Right Vendor

14

Wrap Up, Q&A, and Next Steps

15

Thank You

LogiXMLhttp://www.logixml.comTo learn more, email oem@logixml.com.

Origami Riskhttp://origamirisk.com

16

top related