Cisco Cisco Prime Service Catalog 10.0 Technical References
1-35
Cisco Prime Service Catalog 10.0 Reporting Guide
OL-31037-01
Chapter 1 Advanced Reporting Data Mart
Advanced Reporting Module
Service Start Date and Time
STARTEDATE and STARTEDDATETIME for a service are initially set to the time when the customer
submits the service request. STARTDATE and STARTEDDATTME values are updated as soon as
authorizations are completed and the delivery moment begins. This means that before completion of
authorizations STARTEDATE (TIME) refers to the time the request was submitted; after completion of
authorizations it refers to the data and time the delivery moment began. All computations regarding
standard compliance and task due dates use the actual delivery plan start date.
submits the service request. STARTDATE and STARTEDDATTME values are updated as soon as
authorizations are completed and the delivery moment begins. This means that before completion of
authorizations STARTEDATE (TIME) refers to the time the request was submitted; after completion of
authorizations it refers to the data and time the delivery moment began. All computations regarding
standard compliance and task due dates use the actual delivery plan start date.
Rescheduling a Task
When a task is rescheduled:
•
The new/rescheduled due date for the task is used for on-time calculations for that task.
•
There is no effect on the due date/on-time calculation for the service.
•
The new duration for the task is used in the calculation of standard compliance for the task.
•
The new duration for the task is not used in the calculation of standard compliance for the service.
Creating Reports and Queries
Detailed instructions on using Query Studio and Report Studio are in the User Guides supplied by
IBM/Cognos, which are available from the vendor’s web site. This section addresses concerns specific
to the Service Catalog data mart and the framework that allows query and report builders access to that
data mart.
IBM/Cognos, which are available from the vendor’s web site. This section addresses concerns specific
to the Service Catalog data mart and the framework that allows query and report builders access to that
data mart.
Both tools allow equivalent access to the query subjects and query items exposed in the custom package.
Reports or queries are created simply by dragging items from the Insertable Objects pane at the left of
the page to the Reporting pane. As each item is added to the report, Cognos automatically adjusts the
underlying SQL that is used to retrieve data for the report. To do so, Cognos relies on the relationships
defined in the custom package through which the data mart is exposed. This package includes
relationships between the dynamically defined dictionary-based dimensions and all fact tables. These
relationships rely on database “inner joins”; information on a task or requisition (from the corresponding
fact query subject) will appear in a report containing dictionary-based information only if the dictionary
was used in the service to which the requisition or task applies.
Reports or queries are created simply by dragging items from the Insertable Objects pane at the left of
the page to the Reporting pane. As each item is added to the report, Cognos automatically adjusts the
underlying SQL that is used to retrieve data for the report. To do so, Cognos relies on the relationships
defined in the custom package through which the data mart is exposed. This package includes
relationships between the dynamically defined dictionary-based dimensions and all fact tables. These
relationships rely on database “inner joins”; information on a task or requisition (from the corresponding
fact query subject) will appear in a report containing dictionary-based information only if the dictionary
was used in the service to which the requisition or task applies.
Because Query Studio is an easier tool to use than Report Studio, especially for new users, We
recommend that users start with Query Studio. If they are unable to implement the functionality for the
required report, they may save the query and subsequently edit and enhance it in Report Studio; all
queries created in Query Studio are upward compatible with Report Studio.
recommend that users start with Query Studio. If they are unable to implement the functionality for the
required report, they may save the query and subsequently edit and enhance it in Report Studio; all
queries created in Query Studio are upward compatible with Report Studio.
In particular, the following types of requirements should be implemented using Report Studio:
•
Reports that need to display a “percent of total”, for example, percentage of tasks of a particular type
that were on time or late.
that were on time or late.
•
Reports that need to list requisitions with dictionary data, but have the dictionary data blank for
services in which the dictionary was not used; this can be implemented via master-detail reports in
Report Designer.
services in which the dictionary was not used; this can be implemented via master-detail reports in
Report Designer.
•
Reports with complex filters, for example, in which either one or the other of a condition may apply
for data to be included in the report. (In Query Studio, all filters are logically AND’ed, so that all
conditions must be satisfied for a row to be included in the report.)
for data to be included in the report. (In Query Studio, all filters are logically AND’ed, so that all
conditions must be satisfied for a row to be included in the report.)