This document discusses how to distribute information and answers to the masses through modern reporting at scale. It covers how reporting has evolved from traditional batch-based reporting to more real-time delivery through various methods like embedding in applications. The document also discusses Jaspersoft's product offerings for modern reporting, including its reporting library, server, visualization library and APIs that allow embedding reports in different formats and delivering them in real-time through various methods. It ends with discussing next steps users can take to learn more about Jaspersoft's reporting capabilities.
3. Data as a feature
Winter
Helping Users Reach
Goals with Data
Spring
Embedded BI:
All Things Considered
Summer
Modern Reporting
Fall
Building Data as a Feature
Applications
Hello everyone. Thanks for taking the time to join us today to learn about Modern Reporting at Scale.
SHANE
Reporting is the only type of analytics that does not leave room for interpretation. It is a statement of fact meaning information can be distributed and be interpreted in
SHANE
Why are most people are still making decisions without data? Because the BI industry has tried to solve this problem with one new tool after another. But people want immediate answers to their questions, not tools.
For some, like a data analyst, the answer might come from a dedicated analytics tool. For most though, the answer needs to surface within the applications and collaborative platforms they use every day, not some specialized analytics tool which they will never use.
“Reporting, dashboards, advanced visualization and end-user self-service are given the highest priority initiatives in enterprises focused on making BI a strategic foundation for growth”
Reporting is the only type of analytics that does not leave room for interpretation. It is a statement of fact meaning information can be distributed and be interpreted in
Describe how you do reporting today?
I use jasperreports (just the library)
I use jaspersoft (library + server)
I use another reporting
Any time: reports can be scheduled to run around the clock
Any volume: as customers grow, their reporting demands grow and the volume of reports and schedules multiplies
Any format: as well see later, reports are not for single device consumption any more
role of self-service
requirements
easy to use (excel-like)
control over data access (data-level security)
platform for distribution
Branding / reports are part of a company’s identity
The visualization is the truth. What a report is telling you is consistent over time.
Add bit on consistency and how that improves people’s ability to consume them over time
So we talked about datasources, what about the ways the data is consumed? It’s evolved considerably as well!
Build the slide:
Fully Interactive HTML5 visualizations: change chart types, sort, filter, conditionally format
Excel Output: Data only, no formatting
JSON/XML output: Sometimes the data is for machine consumption
Mobile: View reports on any screens or offline
Embedded: into the 3rd party applications that the 75% access every day
And of course, the traditional pixel perfect exports like PDF, Word, PPT
Reports are data visualizations
The source of truth: now interactive
Integrate visualizations into the app workflow
Avoid having to write microservices to support visualizations
Allow exports of formatted reports and data
Audience implements the information they need, when and in what form
The happiness from control for an individual or group
Reduces or eliminates development backlog
Needs to be easy to use
Data level security
Access available content
Avoid the Excel problem
Can be wrong
Implement standard, locked down reports to be definitions of key information
Here’s another area that we see trending – customers using something other than relational databases to create reports. We’re not talking about data that is sent into a data warehouse, simple operational reports from operational applications.
Our customer, Lufthansa Systems has over 300+ customers which are other airlines, they provide services for them. Innovation is slow in this industry, particurarly when it comes to data but these guys wanted to modernize their stack – one area that their current tools just didn’t work was when data is stored more flexibly
Two projects
In the past 24 months, select all the reporting issues you've dealt with:
Scaling problems (volume, size)
Costing too much
New datasources
More interactivity and more output types required
Report development workload too high
Inability to change data
Other
SLA reqs: as reporting becomes more critical, the expected time (SLA) for delivery gets more closely managed
New apps: more and more apps need embedded reporting
Self service: pressure from business to allow less technical users to create reports
Aging tech: many of the classical reporting tools were made in the early/mid 90’s
Retiring tools: some vendors retiring tech that is in production with less attractive offers (e.g. Oracle but don’t mention )
Prices: lots charge per user
These are the traditional reporting access methods.
SQL: Lets you connect directly and write reports in SQL. Tried and tested!
BATCH: An ETL process allows combining, clensing, and standardizing the data for reporting. Still very important today!
OLAP: Abstracted the complexity of the data. Can be hard to maintain. More for analysis than reporting
So you still have the traditional ones…but now IT has to deal with these
Web Services: The data might be stored in one way but exposed through modern RESTful APIs and Enterprise Service Buses- hiding the complexity of the underlying sources
NoSQL: These new types of databases usually have their own query language for querying and can offer data structures and query languages that are more convenient or purpose built
BigData: Big Data sources need reports too, traditional methods like ETL, OLAP or in-memory processing are not an option here
Federated: This data access method allows a combination of other sources, like a live ETL process – instant access to data mixed with other
Jaspersoft is an embeddable reporting and analytics platform designed for software companies.
Let’s start by doing a quick overview of Jaspersoft. I want to introduce you to a few important aspects of who uses it, what it does, why our platform is particularly well suited for software builders.
Build any type of report, sometimes there are very complex look & feel, data access and logic in reports and we give you everything you could need.
Reporting workbooks
Workbooks, jrPrint process, REST, Scaling, Datasources, Snapshots, CVC, HTML5, data-centric export
REST API
BI tools have always had APIs but they were either very specific to a language (like C++) or were extremely complex. Jaspersoft was one of the first to adopt REST as a standard and it’s extremely easy for a developer to pick up and place reports wherever they want
Visualize.js
Embedding was something that was done since the 1990s when BI started – prorprietary Apis to get reports. but the way we are doing it is completely different. By embedding visualizations through a javascript API we are allowing power, control and ease.
Custom Visualization Component
Need a unique visualization just for your report? We’ve devloped a method for including any type of visualization from any javascript library like d3.js
Infinite- and auto-scale
And with all this comes scale – we want to be able to spin up servers to take care of report load. We can do this easily by running Japsersoft in a clustered environment. We have customers that have to send 100s of thousands of reports to their clients and rely on our scalable architecture
10-15 min Demo:
* report workbooks (see link below)
* Excel Export (see link below)
* Quick demo of REST API
* Schedule a report & send to e-mail
Link to demo files: https://drive.google.com/open?id=0B2e1DOnokfWlbm91V19Uc1g3a2s
In the past 24 months, select all the reporting issues you've dealt with:
Scaling problems (volume, size)
Costing too much
New datasources
More interactivity and more output types required
Report development workload too high
Inability to change data
Other