pam denny maximo qbr adhoc reporting fmmug april2016
TRANSCRIPT
Agenda: Ad Hoc (QBR) Reporting
Value Details Best PracticesReference
MaterialsDemo
1
Maximo Ad Hoc Reporting Value
Reduce Custom ReportsFewer custom reports -> Fewer Costs ->
Improved Upgrade times
Ease of Use
2
Ease of UseStreamlined, Simplified Dialog.
Sig/Performance Options for User Success
Extended FeaturesEditing, Summaries (Min, Max, Avg)
Calculations (Days Overdue)
Ad Hoc Details: Creation
Style
Content
33
Calculate
Summarize
Format
Ad Hoc Creation
44
Detail:
Greatest flexibility in field selection
Ad Hoc: Styles
List:
Greatest flexibility in sorting and grouping
55
Greatest flexibility in field selectionGreatest flexibility in sorting and grouping
Ad Hoc: Apply application query
Takes active
application query
1
66
application query
2
Applies query as
FILTER to ad hoc
report
Difference between Saved and Run Time Where Clauses
Saved: Always used if field checked during report creationIf checked, QBR will ALWAYS execute against saved application query
77
Run Time: Available only if filter (parameter) set during CreationParameter value entered at run time becomes ‘Dynamic Where’
Ad Hoc Creation: Miscellaneous
Title: Must define before
saving report
Share?
*Sig Option Enabled
88
Runs and saves report. Closes dialog.
Cancel: Closes Dialog
Displays report content. Dialog remains Open
*Sig Option Enabled
Ad Hoc Details: Creation
Style
Content
99
Calculate
Summarize
Format
Ad Hoc: Content
10
Ad Hoc: Content
Parent Category
Or ROS (Report Object
Structures)
Parent = Main object of
application
11 Previously called ‘Select’
Children = Related
Objects
Navigate thru ROS
Hierarchy to find/add
fields to your report
Ad Hoc: Content
Available Fields:
Add to your report via
check boxes, hyperlinks or
‘Add..’ buttons
Selected Fields:
12
Selected Fields:
By default, all persistent
list tab fields added.
Can change labels, order or
delete.
Ad Hoc Details: Creation
Style
Content
1313
Calculate
Summarize
Format
User defines calculations on selected attributes
Ad Hoc: Calculations
1414
Calculated values display as COLUMNS on Ad Hoc report
Ad Hoc: Calculations
15
Calculations: Process Flow1. Add attributes to your expression.2. Attributes display in Expression Section3. Data Type defaults to 1st attribute value
1
16
2
3
Calculations: Process Flow
4. Complete Expression adding sql or mathematical functions
5. Input Name (Column Description)
6. Update Data Type if required
7. Test Expression �
17
7. Test Expression �
4
5 6
7
Calculations: Test Expression
Attribute:1. In correct format 2. Available to the user in the Report Object Structure3. Valid value exists (ex. typed in correctly) 4. All attributes within an expression are from the same object
Function1. Functions used are available to user in Expression Library
Checks EXPRESSION for key items including
18
1. Functions used are available to user in Expression Library
Expression1. No division by 0 2. Does not contain another expression
Calculations: Common Issue: Data Types
Selecting correct data type for expression is criticalIf the expression will result in a number:
Select Amount, integer, decimal, duration, or yorn
If the expression will result in a date or date time:Select Date time or time data type
19
Why?Data types are required for mapping to the BIRT Data Set Method
Maximo Database Type BIRT Data Type Data Set Method
YORN String getBooleanString(String attributeName)
DATETIME, TIME DateTime getTimestamp(String attributeName)
Integer Integer getInteger(String attributeName)
Calculations: Common Issue: Data TypesData Type varies by DatabaseExample: Number of days Overdue in Work Order TrackingCalculated as Current Date – Scheduled Finish
OracleExpression: &DATETIME& - SCHEDFINISHData Type: Integer
*Expression: days (&DATETIME&) - days (date(SCHEDFINISH))
20
DB2
Sql Server*Expression: datediff(day, &DATETIME&,SCHEDFINISH)Data Type: Integer
*Expression: days (&DATETIME&) - days (date(SCHEDFINISH))Data Type: Decimal
*function must be added to Expression library
Calculations: Expression LibraryList of sql functions user can add to expression
* Configurable in Report Administration*Prevents sql updates….
21
Calculation: Business Rules…Most Common Question
22Not for distribution
All attributes in expression must be from same object
Calculation: Business Rules1. Attributes can be added to expression - without being a Selected Attribute
from Content Tab
2. Attributes from parent object do not have to be included in the list of expressions.
3. User can create expressions on child and/or grandchild objects - if he follows the hierarchy order
4. The same attribute can be added multiple times to a single expression
23
4. The same attribute can be added multiple times to a single expression
Ad Hoc Details: Creation
Style
Content
2424
Calculate
Summarize
Format
Ad Hoc Summaries
User defines summary functions for selected fields….
2525
…and then summarized values display on Ad Hoc report
Ad Hoc Summaries
26
Summaries: How does it work?
7 Available functions can be applied to fields Total, Count, Average, Minimum, Maximum, Median and Mode
27
Summaries: Process FlowSelect Field Select Function Add Values Available on report 4321
28Not for distribution
1
2
3
4
Listing Report
Summary
Summaries: Results
2929
Report SummaryGrouping Summaries
Grouping Summaries
Summaries: Business Rules
1. Free-Form summary entry is not available (Minimizes errors)
2. Summaries for child object can be added if A minimum of 1 attribute from the child object has been selected on the Content tab
or if an expression has been created on the child object
- > Error message
30
3. Can only add single instance of attribute and summaryExample:Average Work Order Priority from Work Order object can be added once.
Summaries: Business Rules
4. Each data type and summary is not supportedYellow areas below not supported
31
Example: Can not add a Minimum, Maximum of YORN ( 1 or 0) fields
*Additional business rules in Backup Section of presentation
Ad Hoc Details: Creation
Style
Content
3232
Calculate
Summarize
Format
Ad Hoc: Format
33
Edit QBR: Optional
User who creates QBR….can edit it… or use edit it… or use it as base for new QBR
Edit: Best Practices: Key Business Rules
1. Cannot edit QBR if there are future QBR report schedules
Scenario 1 Scenario 2
Today’s Date April 12, 2016 April 12, 2016
QBR Create Date Feb 2, 2016 Feb 2, 2016
ROS Change Date Jan 1, 2016 March 1, 2016
Can edit QBR? Yes No
2. Cannot edit QBR if ROS has changed after the QBR was created
You determine if user can edit QBR if other security groups have access
Via Property setting mxe.report.adhoc.editWithGroupAccess
If yes, QBR owner can edit QBR -
regardless of what security groups
Best Practices: Configure QBR Edit Access
regardless of what security groups
have access
If no, QBR owner cannot edit QBR
when any security group has access
Agenda: Ad Hoc (QBR) Reporting
Overview Details Best PracticesReference
MaterialsDemo
37
Maximo BI Best Practices
Carefully review each security group’s Skill Sets
Database Knowledge
Business Need
Before granting themCreate Report Object Structures
38
Create Report Object Structures
Create Ad Hoc Report
Apply Summaries
Add Calculations
Share report content with others
To insureAccurate report content and
Eliminate negative performance impacts
Best Practices: Report Object Structures
Person creating must be knowledgeable of Maximo database and relationships
Stanley’s WO reportWO for Project XYZPM WO Location 432
Work Order
Report Object
Structure
WO Details For Sup Fred
Planning WO Details for Liz
Overdue WO Location ACD-12
Buffalo’s WO Projections
WO for 87-z122 ProjectMy WO Report
WO for Project XYZPM WO Location 432
Projected WO for Finishing Location
Maximo BI Users
Developer
Admin
Tech
nic
al S
kill
s a
nd
Da
ta K
no
wle
dg
e
Enterprise Report Users
Application User
Power User
Developer
Incr
ea
sin
g T
ech
nic
al S
kill
s a
nd
Da
ta K
no
wle
dg
e
Maximo BI Users: Best Practice – QBR Sig Options
Developer
Admin
Enterprise Report Users
Application User
Power User
Developer
Create QBR Calculate Summarize
Create QBR
Application UserCreate Ad Hoc Reports only
42
Power UserAccess to all Ad Hoc features- Create, Summarize, Calculate and share publicly
43
Agenda: Ad Hoc (QBR) Reporting
Overview Details Best PracticesReference
MaterialsDemo
44
Maximo 76 BI Recorded Demos
25+ Demos on KPIs, Ad Hoc and BIRT Reporting
http://ibm.co/1BZ4nwl
QBR Business Rule Workbook
46
http://www-01.ibm.com/support/docview.wss?uid=swg21695270
QBR Feature Guide
47
http://www-01.ibm.com/support/docview.wss?uid=swg21696691
Maximo 76 Reference Materials
Maximo 76 BI Recordings: http://ibm.co/1BZ4nwl
Maximo 76 Cognos Recordings: http://ibm.co/1HAkF0Q
Maximo 76 BI Documentation: http://ibm.co/1ybttI2Maximo 76 BI Documentation: http://ibm.co/1ybttI2
Maximo Report Wiki: http://ibm.co/13V4RZZ
Maximo 76 BiLogs: http://ibm.co/1Nf81b9
Backup
49
Calculations: Business Rules (Additional)
1. Expression Name does not need to be unique
2. Expression name can contain text, numeric values or special characters
50
1
Calculation: Business Rules (Additional)
3. Data type and category fields are not populated for any attributes added manually
4. Attribute names (Value) only can be used in the expression. Attribute descriptions (Labels) are not allowed.
4
51
4
3
4
Summaries: Business Rules (Additional)
4. Summaries for a grand-child object can be added if - a minimum of 1 attribute from its corresponding parent, and grand-child object has been selected on the Content tab - or added thru a calculation
5. Calculations can not utilize summary expressions
6. Formats of summaries are predefinedDecimal: 2 Decimal Places
52
Decimal: 2 Decimal Places Integer: 0 Decimal Places Dates: One Date Field Date and Time: 2 fields. 1 with Date and 1 Time Duration: HH:MM
7. Editing of summaries is not enabledQuicker to add/delete summaries than to edit