Better BI with Motio & SpotOn Systems

Transcription

1 Better BI with Motio & SpotOn Systems Motio ReportCard SpotOn Vantage Maps Hosted by: Charles Bowen Account Executive, Motio Dave Kerr Technical Marketing Manager, SpotOn

2 Agenda Motio: Document and Analyze your BI Content SpotOn: Enhance your BI with Enterprise Mapping

3 Motio Overview Founded 1999 SDK Consulting S e r v ices B a s e d in Dallas, TX Experts in Cognos SDK over d istinct clients u s ing Services &/or Te chnology We provide tools to help organizations A d a pt Cognos to work with non - sta n d ard s e curity store s S tre amline and automate key aspects of the BI d evelopment p rocess S u rface B I conte nt in a wide va riety of ways

4 Product Driven Customization Automation Improvement Manageability ReportCA+rd MotioCAP MotioCI MotioADF MotioPI Motiovault

5 What is ReportCard? Reports pass through a series of community driven rules Gathers analytics about your BI Implementation Find information about report duplications, inefficiencies, empty reports and identify projects creating non-standard output ReportCA+rd Cloud-based solution Choose Rule Execute Rule Analyze Results Document

6 Areas of Concern and ReportCard Rules ReportCA+rd Performance Consistency Maintainability Usability Readability Execution Time Query Count Find Reports & Sub Queries Find Query Joins Find SQL-based Reports Find Reports w/ Default Names Find Reports w/ Local Classes Empty Report Queries Matching Reports on Duplicate Queries Reports w/out Prompt Pates Matching Cognos UI Elements Empty UI Elements Reports w/ Same Name Non-Prompted Parameter-based Reports

7 Product Screens ReportCA+rd

8 ReportCard Screens ReportCA+rd Create a test suite and choose rules

9 ReportCard Screens ReportCA+rd Results: reports found w/ matching rule criteria

10 ReportCA+rd View the following slides to see a sample of the documentation feature from Motio ReportCard.

11 Report Studio Functional Design Specification Bursted Sales Performance Cognos Version 8.4 Cognos Studio Report Studio Reference 1 Version 1.0 Date Author 25-Feb-2011 Jeremy

12 Title Reference Version Date Bursted Sales Performance Feb-2011 TABLE OF CONTENTS Business Requirements... 3 Request Information...3 Report Background... 3 Functional Design Summary...5 Package... 5 Pages... 5 Queries...5 Functional Design Detail...6 PageSets...6 Page Set Page Set Pages...6 Page List Elements... 7 List1...7 Report Pages... 6 Page List Elements... 7 List1...7 Report Queries...7 Sales Target versus Actual List...7 Report Variables... 8 Page 2 of 9 25-Feb-2011

13 Title Reference Version Date Bursted Sales Performance Feb-2011 BUSINESS REQUIREMENTS The Business Requirements sections define the background and functionality for an individual request for a report and should be completed by the requester. REQUEST INFORMATION The following information is used for contact purposes during all phases of report development and any business question once the report is in production. Report Title A meaningful and unique report title that can be used to identify the report Requestor Department Requestor Name Requestor Contact Request ID 1 Report Version 1.0 Related Request ID If known, please identify related requests by their ID Requested Delivery Provide a target completion date for completion of report development Bursted Sales Performance Go Sales Retail G. Sales gsales@cognossamples.com 02/25/2011 REPORT BACKGROUND Please complete information that should be considered during the design process and also when reviewing requests for change (RFC's) Report Title meaningful and unique report title that can be used to identify the report Report Description Report definition and purpose to provide a meaningful description of the report Report Location Identifies the location of the report within Cognos Connection Business Owners List Business Owners of the report that should approve development and RFC"s Target Users identify user groups and numbers of users that will access the report Acceptable Performance Identify minimum performance requirements such as execution response times Justification Provide reasons for performance requirements Security Requirements Detail any security that should be applied to the report Bursted Sales Performance Scheduled report that delivers sales performance data. Cognos 8.4 G. Sales Cognos End Customers This report is required to run in less than 1 minute. This is a sample report and should not take long to run No security needs Page 3 of 9 25-Feb-2011

14 Title Reference Version Date Bursted Sales Performance Feb-2011 Delivery Method Online, , Subscription Default Format HTML/PDF/Excel/Portal Language Currency Notes Use this section to detail any additional/useful information that should be taken into consideration when developing or changing the above report that is not listed above burst PDF en USD This notes section would contain information on any ReportCard matched rules, if any. Page 4 of 9 25-Feb-2011

15 Title Reference Version Date Bursted Sales Performance Feb-2011 FUNCTIONAL DESIGN SUMMARY The functional design summary shows the packages, pages and queries used throughout the report. You can navigate to the detail within each section by clicking on the hyperlink provided. PACKAGE This section is a summary of the report content. Every Cognos report is linked to a package, this report is linked to the 'GO Data Warehouse (query)' package. Package Name Package Search Path GO Data Warehouse (query) /content/package[@name='go Data Warehouse (query)']/model[@name='model'] PAGES REPORT PAGES The report page is a container for the report layout objects that you used to build the report. A page is made up of page header (optional), page body (mandatory) or page footer (optional). The following section defines all the objects that have been developed on the report page. For example List, crosstab, chart, map, repeater etc. Page Name Page1 QUERIES The report contains the following queries: (Use the hyperlinks to jump to the query definitions) Query Name Source Type Sales Target versus Actual List Page 5 of 9 25-Feb-2011

16 Title Reference Version Date Bursted Sales Performance Feb-2011 FUNCTIONAL DESIGN DETAIL The functional design detail section of the reports provides content for the page prompts, page sets, report pages, singletons, lists, charts, html, joins, queries, filters and variables. The section has hyperlinks to the relevant section. PAGE SETS Page sets have been defined to associated pages within a specified group or level that indicates the page set is to be repeated for that group or level. For example, render a specified set of pages for each country in the query. PAGE SET1 Query Grouping Sorting Sales Target versus Actual List Employee name PAGE SET1 PAGES The set of pages to render according to a grouping structure. Page Name Page1 REPORT PAGES The report page is a container for the report layout objects that you used to build the report. A page is made up of page header (optional), page body (mandatory) or page footer (optional). The following section defines all the objects that have been developed on the report page. For example List, crosstab, chart, map, repeater etc. PAGE1 PAGE1 OVERVIEW PAGE1 PROPERTIES Page Query Master Detail Relationship Style Variable Render Variable Page 6 of 9 25-Feb-2011

17 Title Reference Version Date Bursted Sales Performance Feb-2011 PAGE1 VALUE PROMPTS The prompt value sections details all the prompts and parameters defined on the report page. The prompts have been included to the report to add interactivity for users. Prompts act as questions that help users to customise the information in a report to suit their own needs. LIST ELEMENTS Use list reports to show detailed information from your database, such as product lists and customer lists. A list report is a report that shows data in rows and columns. Each column shows all the values for a data item in the database or a calculation based on data items in the database. LIST1 List Name List Query Grouping List1 Sales Target versus Actual List Employee name Percentage of Plan Employee name Total(Quarterly Sales target) Total(Revenue) Total(Variance) Product line Total(Quarterly Sales target) Total(Revenue) Total(Variance) REPORT QUERIES Queries determine what data items appear in the report. Sometimes you want detailed rows of data, which you obtain by using a simple SELECT statement. Other times you must calculate totals or averages using summary functions and grouped columns or must apply filters to show only the data you want. SALES TARGET VERSUS ACTUAL LIST Data Item Aggregate Rollup Aggregate Sort Expression Employee name None Automatic Don't Sort [Sales (query)].[employee by organ ization].[employee name] Page 7 of 9 25-Feb-2011

18 Title Reference Version Date Bursted Sales Performance Feb-2011 Product line None Automatic Don't Sort [Sales (query)].[product].[product line] Product type None Automatic Don't Sort [Sales (query)].[product].[product type] Revenue Total Automatic Don't Sort [Sales (query)].[sales fact].[reve nue] ManagerID Automatic Automatic Don't Sort lower(substring('aron',1,1)+'adels vard') Burst_Key Automatic Automatic Don't Sort [ManagerID]+'@grtd123.com' Quarterly Sales t arget Total Automatic Don't Sort [Sales target (query)].[sales target fact].[sales target] Variance Automatic Automatic Don't Sort [Revenue]-[Quarterly Sales target] Total(Quarterly S ales target) Calculated Total Don't Sort [Quarterly Sales target] Total(Revenue) Calculated Total Don't Sort [Revenue] Total(Variance) Calculated Total Don't Sort [Variance] Percentage of P lan Total Percent of Plan Automatic Automatic Don't Sort total([revenue]) / total([quarterly Sales target]) Automatic Automatic Don't Sort total([revenue]for report)/total([ Quarterly Sales target]for report) SALES TARGET VERSUS ACTUAL LIST FILTER DETAIL A filter is set of conditions in a query that narrow the scope of the data returned. A detail filter is applied before aggregation is complete. Expression Usage Application [Sales (query)].[time dimension]. [Quarter key]=20071 Required Before Auto Aggregation [go_data_warehouse].[2007] Required Before Auto Aggregation [go_data_warehouse].[go Northern Europe] REPORT VARIABLES Required Before Auto Aggregation A report variable allows the report to contain prompt filters, conditional formatting or conditional rendering to your report. Variable Name Values 1 Type Report Expression Quarterly Sales Missed Variable boolean [Sales Target versus Actual List].[Variance]<0 Variable Name Language variable Page 8 of 9 25-Feb-2011

19 Title Reference Version Date Bursted Sales Performance Feb-2011 Values Type Report Expression zh fr de ja ru zh-tw it ko pt-br es locale ReportLocale() Page 9 of 9 25-Feb-2011

20 Better BI with SpotOn Systems and Motio Motio Report Card SpotOn Vantage Maps

21 SpotOn Vantage Maps Demand for Maps in Business Impact of Spatial Lens on business Map integration for report authors Architectural value

22 SpotOn Systems Inc. World-leading leading BI GIS Integrators IBM Cognos BI Expertise Award-winning integration Esri ArcGIS Expertise Only Esri Map Integration Solution Deep IBM Cognos architectural knowledge

23 BARRIERS to MAP INTEGRATION Limited Functionality Development Costs Slowed Deployment Enterprise Readiness

24 SUCCESS CRITERIA Value to the business Empower the report author Enterprise readiness

25 Built for the Report Author Select map layers Spatially organize Map-report interaction

26 Demonstration:

27 Flexible Enterprise GBI Architecture IBM Cognos BI arcgis.com (Esri Cloud Map Services) SpotOn Vantage Maps ArcGIS Server Cloud-based Map Services (SpotOn Map Starter)

28 Have a conversation with us Download and share the demo Motio contact: Charles Bowen cbowen@motio.com SpotOn contact: Mike Boryski Mike.boryski@spotonsystems.com ext THANK YOU