Getting Started With Embedded Analytics: 4 Things To Know

oie_tcsPh5eDqQ8P

The folks over at Sisense recently published an interesting blog post: A Beginner’s Guide to Embedded Data Analytics. It seems like there’s a lot of value here, so I thought I’d go ahead and summarize the post and provide my take. Eran Levy, the post’s author, notes that no matter whether you are in producing automation software, SaaS products, or cloud applications, the reason why enterprise companies are becoming increasingly interested in this kind of stuff is because they are collecting lots of data.

Not only are businesses collecting lots of data, but they are starting to realize the value it adds to their organizations. Embedding powerful BI and data analytics tools within existing applications can give your product a competitive edge. Before jumping in, the author recommends you weigh the following:

1. Do you buy or build?

This one is simple. You want to add an embedded BI feature to your application. Do you want to buy an existing embeddable software and integrate it or develop an analytics platform on-premise? The author makes the claim that in a perfect world the choice would be to keep everything in-house to retain full control and include exactly the kinds of capabilities that your clients will find useful.

In reality though, BI is not a necessity for most organizations, and developing a platform from scratch could take a long time and cost a pretty penny. From a developmental standpoint, visualization tools don’t require an extreme amount of work, but a great BI tool is about more than just looks; it also needs to perform.

So this type of platform is tough to develop and would cost a lot. Even if you were to get past those obstacles, you might still fail to achieve the level of functionality that your customers would expect from an out-of-box solution. It looks like our decision has been made for us.

2. Ease of implementation

The author throws us a curveball here, saying: “Having said that, you also shouldn’t overlook the possible hidden costs and time-sinks that come with some embedded solutions.”

Integration issues between your own software and the embedded analytics platform you chose have the potential to increase cost and production time. Nothing good comes as a result of those two factors. Time can become a factor, as developmental edits between you and your BI provider will need to take place.

In addition, some BI software is quite complex, meaning that there will be an increased period of training before the system goes live. As a result, the cost is exaggerated, and time to market is slowed. Going the external route of buying an embedded BI feature is not the end all either, as it doesn’t guarantee faster turnaround, making it important to test a potential solution thoroughly before deciding on it.

3. Defining requirements

There are a wide variety of BI solutions out there, and all of them do interesting things. In digging deeper though, one might find that the differences between them is substantial. The author notes: “The type of tool you’ll require depends, among others, on the volume, variety, and velocity of the data you plan to process.” Things to consider:

  • Size: How much data will you need to handle? Some tools are only designed to handle a certain amount of data before performance suffers
  • Reporting: Will users have the ability to generate custom reports and queries, or will pre-loaded reports do the trick?
  • Security: Can permissions be set on databases, tables, and row levels? What kind of permissions does the solution allow?
  • Data Complexity: Is your data organized, or are you dealing with integration from multiple complex sources?

4. Underestimating future needs is a mistake

The author makes a fantastic point here when he says ” The amounts and types of data we collect today would have been incomprehensible a few years ago, and there’s no reason to believe they will remain identical in a few years’ time.” He’s right, so putting all of your eggs in one basket is not ideal.

It would be wise to put scalability high up on your embedded analytics wish list so you can ensure flexibility at a later date. You’ve got to assume that whatever kinds of data you are dealing with now will grow in number, frequency, and complexity. Will the solution you buy to develop be able to handle those demands in a year from now?

Get a free Business Intelligence Buyers Guide for an industry overview, along with profiles of all the top vendors, or get a free Buyers Matrix Report for a more in-depth look, along with a side-by-side comparison of what each solution offers.

Timothy King
Follow Tim