Download Actuate e.Services Basic Template

PSBI Reporting Analysis & Recommendations
Disclaimer:
This Document is intended as a discussion framework only.
Confidentiality:
This Document is the confidential information of Actuate and belongs solely to
Actuate. Furthermore the reader agrees that this document is of substantial
value to Actuate and such value would be impaired if the information contained
herein were disclosed to anyone outside Actuate except as authorized by
Actuate.
Revision History
Rev#
Date
Primary Author(s)
Description
1.0
04/17/2009
Ralph Gleason
Initial Document
1.1
04/21/2009
Ralph Gleason
Report Design
Recommendations.
Document Review History
Acceptance indicates that the document is complete and fairly represents the needs of its
customers. Once accepted, the document enters into formal change control.
Rev#
Date Accepted
Reviewer Name
Responsibility
1.0
* = No official acceptance received. Accepted by default.
ACTUATE CONFIDENTIAL
81962816
Last Saved 8/13/17
Page 1 of 14
TABLE OF CONTENTS
1
REPORTING ANALYSIS & REVIEW ................................................................. 3
1.1
1.2
1.3
1.4
1.5
1.6
2
PSBI REPORTING DESCRIPTION ...................................................................... 6
2.1
2.2
2.3
2.4
2.5
2.6
3
ABSTRACT ........................................................................................................... 3
INTRODUCTION .................................................................................................... 3
FAA REPORT(S) DESCRIPTION AND ANALYSIS .................................................... 3
PSBI REPORTING OPTIONS OVERVIEW ................................................................ 4
VIEWS DATA MART OVERVIEW ........................................................................... 5
ACTUATE INFORMATION OBJECTS OVERVIEW ..................................................... 5
REPORT TERMINOLOGY ....................................................................................... 6
REPORTING OPTIONS FEATURES .......................................................................... 8
INFORMATION OBJECT TERMINOLOGY................................................................. 9
INFORMATION OBJECT FEATURES ........................................................................ 9
DATA MART TERMINOLOGY .............................................................................. 10
DATA MART FEATURES ..................................................................................... 11
REPORT RECOMMENDATION ........................................................................ 12
3.1
3.2
3.3
DESIGN APPROACH ............................................................................................ 12
PROCESS FLOW .................................................................................................. 12
RISKS INVOLVED................................................................................................ 12
4
REFERENCES ........................................................................................................ 13
5
QUESTIONS ........................................................................................................... 14
5.1
5.2
QUESTION 1?...................................................................................................... 14
QUESTION 2?...................................................................................................... 14
ACTUATE CONFIDENTIAL
81962816
Last Saved 8/13/17
Page 2 of 14
1 REPORTING ANALYSIS & REVIEW
1.1 ABSTRACT
This is document outlines current management report(s) based on <put “the givens” here,
basically anything you can set as a set of assumptions>. All references to report designs
contained in this document are intended as conceptual design options. The actual report design
process is done in subsequent phases with more detail. The goal of this document is to provide
the <Client> with a recommended approach and an initial estimate based on the
recommendations, to design and implement custom reports.
1.2 INTRODUCTION
The <Client> uses data from <data source location> to measure customer satisfaction, operational
performance, and financial performance. Performance measures and fact data is entered into
<Client Application> is then summarized into a number of reports and shared at <for example:
monthly and quarterly > management meetings, using a <Power Point slide deck, Excel, Web…>
containing <some relevant information, to describe how the reports are used>. To help
standardize and automate part or all of the report development process, <Client> will utilize an
integrated custom reporting solution.
1.3 <CLIENT> REPORT(S) DESCRIPTION AND ANALYSIS
1.3.1
OBSERVED REPORT CHARACTERISTICS
The assumptions described here are based on the materials presented at the Management
Meeting, from the 80+ slides with the file name:
(New Briefing Structure Views Charts reports.ppt)
<Client> Reports can be categorized into four major category types;
1 – Summary Report.
2 – Combination Chart Reports.
*note*
sections shown after C-1 contain a variety of chart types
It is assumed that either multiple reports will exist, conditional
chart types will exist, OR all bar charts will be of the
Combination-Chart with Bar and Line graphing.
3 – Quad Chart Reports.
4 – Detail listing Reports.
Four primary report chart styles or types are represented in the Management meeting Power
Point Slide deck. The styles vary slightly across subsections of the three major ‘Strategic Themes’,
and depending upon the submitting Unit. A benefit of report automation is higher consistency in
report style, though <Client> may opt to apply charts as requested by users and managers.
ACTUATE CONFIDENTIAL
81962816
Last Saved 8/13/17
Page 3 of 14
Based on the most recent Power Point slide deck, the <Client> has nine variations in chart styles
as follows:
1 – Bar Chart
1
2 – Stacked Bar
1
3 – Stacked Bar Combo (single line - Red)
2
4 – Stacked Bar Combo (multi line – Red/Blue)
1
5 – Multi Bar Combo (single line – Red)
4
6 – Single Bar Combo (single line – Red)
19
7 – Single Bar Combo (multi line – Red/Green)
2
8 – Multi Bar Combo with Table (single line – Red)
1
9 – Single Bar Combo with Table (single line – Red)
1
A Title slide precedes each section containing a series of each chart type previously described.
The Title slide is based on each of the <Client> “Strategic Themes” from their Views Map.
1.3.2
NOTABLE REPORT CHARACTERISTICS
Except a few “hand entered” comments, the data contained within the reports can reasonably
come from <Source>. The example report also contains images. Images can be either static or
dynamic. Additionally, images can be embedded, locally referenced, referenced from a URL, or
be pulled in from a Database.
In the case of the <Client> report slides containing a graph one or more of three “Code Key”
images will be required. The inclusion must be determined by some identifiable data attribute
related to the slide(s) / Graphs. Additionally the “Polarity” indicator arrow found on some
reports is also a dynamic image. The “High is Good/Bad” images will need to be conditionally
referenced by the report if they are to be used.
Given that all the data <Client> requires for their reports exists within Views, the design will use
Views Categories to control the content and pagination of the report. To do this the design must
include a mapping of all report elements (Chart elements, Title Elements, List Elements, etc...)
back to the View being reported on. By mapping back to the View, all measures, locations, and
data will be accounted for. The Categories will work to group various Views data in a way that
the report groupings will control the report at run-time. A design layout map / diagram can be
found in the appendix of this document.
1.4 PSBI REPORTING OPTIONS OVERVIEW
Your Performancesoft Views implementation includes four integrated interactive reporting tools.
Two Desktop designers, a Web enabled ad hoc report builder, and an Interactive Report Viewer.
Understanding the purpose and capabilities of each reporting option will ensure maximum
utilization and benefit of Performancesoft PSBI.
BIRT and e.Spreadsheet, are installed on Report Developer Desktops and are used to create
custom report designs. The BIRT Designer is used to create interactive reports that can be output
in many formats including Power Point. The e.Spreadsheet Designer is used to create interactive
reports that open natively in Excel right from the Reporting Web Server.
Business Report Studio (BRS) and Interactive Viewer (IV) are Web enabled fully functional ad
hoc reporting applications. To use BRS or IV a user will need rights to the Web Server and
Application, and Internet Explorer. Using BRS a user can create an ad hoc report from scratch
ACTUATE CONFIDENTIAL
81962816
Last Saved 8/13/17
Page 4 of 14
using a standard template or a custom template designed using BIRT. BRS can also open and
modify an existing report. IV is an option that can be enabled when viewing a report on the
Report Server. With IV, users can make report versions of their own changing the layout, hiding
report elements, sorting columns, and more without formally requesting a report design change.
1.5 DATA MART OVERVIEW
The Performancesoft Views Data Mart is a relational multi-dimensional database schema. The
Data Mart is optimized to efficiently store and process large amounts of analytical data.
Performancesoft Views includes a configurable “Extract Transform and Load” (ETL) process
application. This ETL process application converts your Performancesoft Views data into a report
friendly schema. The converted Performancesoft Views data is then written to either a SQL
Server or ORACLE data repository.
As of Views version 7.3.1 Data mart consists of 23 tables, 1 User Defined Function and 4 Views.
The Entire set of Data Mart tables is divided into 4 categories. The report design process will
involve mapping report entities through Data Mart tables and attributes.
1.6 INFORMATION OBJECTS OVERVIEW
Performancesoft Views implements standard Information Objects that utilize a real-time web
services interface to Performancesoft Views databases. These standard Information Objects are
intended for very specific highly focused data access. As such highly analytical data, particularly
the data used in broad scope reporting will require custom Information Objects built against the
Performancesoft Views Data Mart.
Information Objects are required by Business Report Studio and are highly reusable. As such it is
recommended that Actuate develop FAA-specific Information Objects to support FAA reporting
data sets. By implementing Information Objects FAA will standardize queries, eliminate the need
for users to understand the Data Mart and SQL in order to develop reports, and ultimately
simplify managing reporting data.
ACTUATE CONFIDENTIAL
81962816
Last Saved 8/13/17
Page 5 of 14
2 <CLIENT> REPORTING DESCRIPTION
This section describes some terminology used in and features of the three major areas of PSBI
Reporting, “Reports”, “Data Mart”, and “Information Objects”.
2.1 REPORT TERMINOLOGY
2.1.1
CASCADING PARAMETERS
Report parameters having a hierarchical relationship. For example (Country, State, City).
2.1.2
CHART
A chart is a graphic representation of data or the relationship among sets of data.
2.1.3
CHART ELEMENT
A report item that displays values from data rows in the form of a chart. The Chart element can
use data rows from the report design’s data set or a different independent data set.
2.1.4
DATA
Information that is stored in databases, flat files, or other data sources that can appear in a report.
Though Views is referred to as a “database” the context for the purpose of a report is generally
limited to the “database” to mean a “relational database”.
2.1.5
DATA SET PARAMETER
A parameter that is associated with a Data Set column and passes an expression to extend
dynamically the query’s WHERE clause. A Data Set Parameter restricts the number of rows that
the data set supplies to a report.
2.1.6
DATA SOURCE
The “Connection” to the data used in the report. This can be any number of sources using BIRT.
2.1.7
DESIGN
A Report Specification as a formal document. Designing a report includes selecting data, laying
out the report visually, and saving the layout in a report design file. This is referring to both the
specifications as well as the act of designing a report.
2.1.8
ENTERPRISE
A large collection of networked computers that run on multiple platforms, sometimes referred to
as a “managed Environment”.
2.1.9
ENTERPRISE REPORTING
Enterprise reporting can be defined as the regular provision or dissemination of information in
the form of reports, graphs, dash boards, and more to decision-makers in an organization.
ACTUATE CONFIDENTIAL
81962816
Last Saved 8/13/17
Page 6 of 14
Reports are typically available as either executable, or cached on a centralized server. With
Actuate BRS, reports can also be built ‘on-the-fly’ over the web or intranet with no special
applications required.
2.1.10 GROUP
A set of data rows that have one or more column values in common.
2.1.11 GROUP KEY
A data set column that is used to group and sort data in a report.
2.1.12 HEADER
The unit of information found at the top of each page of a report.
2.1.13 IMAGE
An image is a graphic that appears in a report. BIRT Report Designer supports; GIF, JPG, and
PNG file types.
2.1.14 LAYOUT
The “Layout” is the designed appearance of a report. Designing the layout of a report involves
placing report items on a page and arranging them in a way that helps the user analyze the
information easily.
2.1.15 LIBRARY
A library is a collection of reusable and shareable report elements. A library can contain
embedded images, styles, visual elements, JavaScript code, data sources, and data sets.
2.1.16 PARAMETER
A parameter is a report element that provides input to the execution of a report. Parameters
provide control over report data selection, processing, and formatting.
2.1.17 REPORT
A report is one of a category of documents that presents formatted and structured content from a
data source, such as a database or text file.
2.1.18 REPORT DESIGN FILE
A report design file is the core design of a report. In the case of report design files for
Performancesoft Views, these can be either [.rptdesign] for BIRT reports, [.sod] for e.Spreadsheet
reports, or [.bizdesign] for BRS reports.
2.1.19 SECTION
A section is a horizontal band in a report design. Sections structure and format related report
items.
ACTUATE CONFIDENTIAL
81962816
Last Saved 8/13/17
Page 7 of 14
2.1.20 TEMPLATE
In BIRT Report Designer, a predefined structure for a report design. A report developer uses
templates to maintain consistent report design styles across a set of report designs, streamlining
the report design process.
2.2 REPORTING OPTIONS FEATURES
2.2.1
o
o
o
o
o
o
2.2.2
BUSINESS INTELLIGENCE REPORTING TOOL (BIRT)
BIRT Report Designers produce rich, highly interactive and navigable reports with
formatting, graphic, and conditional display options to meet complex requirements.
BIRT Report Designers use the drag and drop, WYSIWYG design paradigm of familiar
development tools such as Web-page designers, and web-band desktop publishing
products for easy report development.
BIRT Report Designers offer task-specific editors, builders and helpers such as wizards
and cheat sheets that make it easy for developers of all skill levels to create reusable
templates and reports.
BIRT Report Designers support component and design template reuse.
BIRT Report Designers efficiently integrate data from multiple data sources, transform
the data and manipulate the data based on business logic .
BIRT Report Designers offer programmatic control using standard languages and
interfaces for nearly every aspect of report layout, data access, data transformation and
report rendering.
BUSINESS REPORT STUDIO (BRS)
As an accessible BIRT business-user product, BIRT Report Studio adds value to the BIRT product
line.
o
o
o
o
o
o
2.2.3
Saves time, because re-usable templates and themes can be set up and passed between
BIRT products
Conserves IT resources, as Actuate BIRT products facilitate self-service report creation
Lets business users create ad-hoc reports
Reduces reporting bottlenecks in IT and improves requirements understanding between
IT and end users
Lowers costs by eliminating training expenditures
Increases ROI
INTERACTIVE VIEWER (IV)
As the most accessible BIRT end-user product to date, Actuate BIRT Interactive Viewer adds
value to the BIRT product line.
o
o
o
Allow virtually anyone to access, personalize and customize a BIRT report without
affecting underlying data
Give users immediate access to information and an immediate return for their efforts, in
effect teaching them how to use the basic BIRT tools
Shift IT focus from report generation activities to higher-level priorities—ease of use
shortens cycles between report design and completion
ACTUATE CONFIDENTIAL
81962816
Last Saved 8/13/17
Page 8 of 14
o
Introduce BIRT open source-based products to the entire enterprise, paving the way for
future BIRT development and deployment
2.3 INFORMATION OBJECT TERMINOLOGY
2.3.1
CONNECTION DEFINITION (DCD) FILE
Connection Definition files contain the Source Data connection values and drivers.
2.3.2
MAP (SMA) FILE
Map files contain the SQL, Joins, Aliases, and other properties to create map tables which are
used by Information Objects.
2.3.3
INFORMATION OBJECT (IOB) FILE
Information Object files are reusable encapsulated SQL Queries used as data sources by all
Actuate products.
2.3.4
PARAMETER
See “Parameter” in the BIRT section.
2.3.5
JOIN
Two or more tables or Information Objects connected by a key field, to make a resulting
“combined” table.
2.4 INFORMATION OBJECT FEATURES
2.4.1
INFORMATION OBJECT DESIGNER (DEVELOPER)
BIRT Designer Compatibility
Actuate Information Object Designer is compatible with Actuate BIRT Designers.
o
Data access flexibility - supports the same data sources as the BIRT Designers.
o
Component -based reuse - create components to be included in the BIRT report libraries
for use in multiple reports.
Visual development environment
Actuate Information Object Designer is a highly graphical, visual development environment to create
Information Objects that specify data sources, calculated fields, and meta-data names for fields and
columns.
o
Explicit query definitions-supports pre-setting specific queries and explicitly specifying
how queries should execute and return results.
ACTUATE CONFIDENTIAL
81962816
Last Saved 8/13/17
Page 9 of 14
o
Role-based access control-supports controlling which information users can receive,
based user role and access privileges. Filters and conditions can be applied to allow
personalized views of data for each user.
.
2.4.2
o
o
o
o
o
INFORMATION OBJECT (USER)
Query enterprise data without training – Actuate Query data is delivered through a fivetab wizard that allows end users to select, sort and summarize data from Information
Objects. The interface requires no training, yet provides the flexibility users need to
obtain the desired data from within their existing portal or reporting applications
Save and share query definitions and results – Users can save their query definitions for
future execution and share these definitions with their peers
Output data in multiple formats – Users can select to output their data as a simple stylesheet driven html page or PDF document. The data can be opened in Excel or Actuate
e.Analysis for graphical representations.
Halt runaway queries – IT defines how data is presented, how it is secured, and what
users can actually do with it; because data is supplied through Information Objects, IT
has complete control over result set size, query complexity and security to eliminate the
possibility of runaway queries or abuses to the system.
Customize and extend IT-built query applications – Actuate Query wizard tabs can be
customized and extended by IT. The wizard automatically recognizes required and
optional query parameters provided through Information Objects. IT can extend this
model to further simplify or specifically tailor exactly which data users access
2.5 DATA MART TERMINOLOGY
2.5.1
STAR SCHEMA
Standard structural configuration of relational database tables that is highly efficient, capable of
processing large amounts of data, and report friendly.
2.5.2
QUERY
Structured Query Language (SQL) written to obtain specific data based on a specific request.
2.5.3
DIMENSION
A modeled entity which is usually described in a physical sense; however for the Views Data
Mart Dimensions are Measures, Locations, Period, etc... the entities within views described as
“objects” rather than “data”.
2.5.4
FACT
A modeled entity which represents a “data” attribute in Views. For example “calculated data”
are the “Values” of some “Actual” or “Target”.
ACTUATE CONFIDENTIAL
81962816
Last Saved 8/13/17
Page 10 of 14
2.6 DATA MART FEATURES
2.6.1
PRE-BUILT USER DEFINED FUNCTIONS.
The Views Data Mart contains a highly structured schema that on its own is very report query
friendly. Over time certain queries or formulas or functions have been found to be utilized
frequently. These have been categorized and a set of standard functions (UDF’s) have been
developed.
2.6.2
COMPATIBLE WITH SQL SERVER OR ORACLE
2.6.3
CONFIGURABLE IN VIEWS ADMINISTRATOR
ACTUATE CONFIDENTIAL
81962816
Last Saved 8/13/17
Page 11 of 14
3 REPORT RECOMMENDATION
3.1 DESIGN APPROACH
What is the overall design approach? What is the rationale behind this? If multiple approaches are
available list all and the context to apply them on a project. A high-level decision tree is preferred.
3.2 PROCESS FLOW
Explain the process flow. A schematic representation would be preferred.
3.3 LEVEL OF EFFORT ESTIMATES
What is the estimated effort required to complete the various stages of the process flow?
3.4 RISKS INVOLVED
What are the risks involved with - using and not using this approach?
.
ACTUATE CONFIDENTIAL
81962816
Last Saved 8/13/17
Page 12 of 14
4 REFERENCES
Indicate manuals or web site URLs for further reading about this topic.
ACTUATE CONFIDENTIAL
81962816
Last Saved 8/13/17
Page 13 of 14
5 QUESTIONS
5.1 QUESTION 1?
Answer.
5.2 QUESTION 2?
Answer.
ACTUATE CONFIDENTIAL
81962816
Last Saved 8/13/17
Page 14 of 14