Event Studio - dbmanagement.info

Event Studio
Cognos 8 BI
Objectives
 In this module, we will examine:

Event Studio Overview

Event Studio features

Event Lifecycle Management

Workflow of tasks
What is Event Studio?
 Event Studio is a new studio that is fully integrated into the Cognos 8
platform.
 Event Studio enables users to be notified of key operational or
performance related events that may affect the business.
 Unlike OLAP or Metrics (which work with summarized data), Event
Studio is used to identify individual problems or opportunities.
 Use OLAP/Metrics to discover what works and what doesn’t. Use
Event Studio to discover when things that work (or don’t work) are
happening, so you can exploit (or fix) them.
 Event Studio can:

alert users

deliver information about the event

automate tasks
What does Event Studio Do?
 Event Studio automatically monitors data for the events you have
defined.
 When an event is detected, Event Studio can:

send alerts by email

run reports concerning the event

run an existing Agent

update a database

incorporate a Web service

post ‘newsflashes’ to the portal

run an Import\Export

run a content Maintenance Task

run a Metrics Task
Additional Features
 Event Studio also allows users to:

create Parameters (Prompts) for use in conditions

must modify agent after creation in Cognos Connection

create calculated items for use in tasks

create and apply a schedule to an agent

manage the task execution rules

re-order the tasks

preview results

manage notification lists
How Does Event Studio Help?
 Users don’t have to read reports looking for problems to deal with.
Event Studio notifies them about problems as soon as they occur.
 Detecting events as soon as they occur means there is a better
chance of achieving a favorable outcome.
 Identifying and detecting the most important issues means that
users’ workloads are automatically prioritized.
 Using Event Studio:

avoids information overload

allows users to keep track of individual events

helps keep Metrics ‘green’.
Event Lifecycle Management – Agents
 Agent

manages Event Lifecycle Management
automatically

Event Studio creates and maintains
Agents

Event condition – detects significant
events

Correlates events

Workflow of tasks – drives actions
according to status

Schedule
 Agents run unattended

Detects events, running tasks and
maintains a list of current issues
Event Studio
Tasks
Condition
Detecting a Significant Event
 An event occurs when data meets a condition.
 The data conditions that signify an event may apply to single or
multiple systems.
Returns = ' our fault ' and ( Order Value > $5K or Customer debt > $50K )
Data
Warehouse
Returns
Orders
Drive Action – Workflow of Tasks
 Where human interaction is required
 Timely delivery of event related information
 Email message
 Dynamically maintained portal messages – BI Newsflash
 Reports
Communicate complete
picture of the event and
facilitate action
Tasks Can Run in Context of the Event
Report
Agent
Sunglass Corner
Taeho Sports
Information focused on the specific events
Tasks Can Run in Context of the Event (cont’d)
Returns = ' our fault ' and (Order Value >
$5K or Customer debt > $50K)
Agent
Agent
Customer debt > $50K
Sunglass Corner
Taeho Sports
Where
Customer IN (Sunglass Corner, Taeho Sports)
Cross-system event lifecycle management escalation
Drive Action – Workflow of Tasks
 Automated actions:

Agent

Web Service

Run database-stored procedure
Further event validation
Escalate
Information gathering
Initiate an action
Event Correlation and Task Workflow
 Events have a lifecycle.
 New event instances are correlated with prior ones.
 Events can be:

New

Ongoing - changed

Ongoing - unchanged

Stopped
Event Lifecycle
Tasks Are Performed According to their State
in Lifecycle
Returns = ' our fault ' and ( Order Value > $5K
or Customer debt > $50K )
New
Ongoing - Changed
- unchanged
Stopped
1. Email sales rep
2. Detail report to
order fulfilment
Escalate to Manager
Notify accounts
Tasks Are Performed According to their State
in Lifecycle (cont’d)
Current and Prior Agent Run Values
Period 1
Period 2
What is new? What is still ongoing? What has stopped?
Summary - Tasks
 Drive action

human

automated
 Tasks are performed

in context - the events identified - current and prior

according to their status
Summary – Event Lifecycle Management
 Agent

Event condition



detect significant events
Workflow of tasks

drive actions

in context

and by status
Schedule
 Agent Hot List
Summary
 In this module, we examined:

Event Studio Overview

Event Studio features

Event Lifecycle Management

Workflow of tasks
Workshop 1
 Event Studio